From: Jurgen Philippaerts <jurgen@pophost.eunet.be>
To: linux-kernel@vger.kernel.org
Subject: Re: arch/sparc64/kernel/traps.c
Date: Thu, 11 Apr 2002 12:34:44 +0200 [thread overview]
Message-ID: <20020411103444.GA7280@sparkie.is.traumatized.org> (raw)
In-Reply-To: <20020409212000.GK9996@sparkie.is.traumatized.org> <20020409.155757.34666328.davem@redhat.com> <20020410133908.GJ11858@sparkie.is.traumatized.org> <200204110547.g3B5l3X08802@Port.imtp.ilyichevsk.odessa.ua>
On Thu, Apr 11, 2002 at 08:00:08AM +0200, Denis Vlasenko wrote:
> > > ksymoops should be already installed on your system
> > > at /usr/bin/ksymoops, if it isn't find the package
> > > to install or complain to your distribution maintainer :-)
> > >
> > > If you still want to compile ksymoops from source you need to update
> > > and install a new binutils to get the latest BFD library.
> >
> > allright, ksymoops doesn't come with my distribution (Splack)
> > so i got the source, and went from there.
> >
> > now it compiled nicely.
> >
> > here's the output that i get (i'm not quite sure what to expect, so i
> > hope this is what you need:)
>
> [snip]
>
> > Error (Oops_bfd_perror): set_section_contents Bad value
>
> [snip]
>
> I've seen the same when ksymoops was linked against old libbfd.
> It builds without errors but could not disassemble oopsed code.
> Check for old libbfd lying around.
sorry for the long lines, but it would't be very readable otherwise
:)
$ locate libbfd | xargs ls -ld
-rwxr-xr-x 1 root root 632951 Apr 10 15:18 /usr/lib/libbfd-2.12.so
-rw-r--r-- 1 root root 737648 Apr 10 15:18 /usr/lib/libbfd.a
-rwxr-xr-x 1 root root 771 Apr 10 15:18 /usr/lib/libbfd.la
lrwxrwxrwx 1 root root 14 Apr 10 15:24 /usr/lib/libbfd.so -> libbfd-2.12.so
$ locate bfd.h | xargs ls -ld
-rw-r--r-- 1 root root 134077 Apr 10 15:18 /usr/include/bfd.h
it all looks like the new version to me
ps: it's the first time i actually use ksymoops, so excuse my
newbie-like behaviour :)
Jurgen.
next prev parent reply other threads:[~2002-04-11 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 21:20 arch/sparc64/kernel/traps.c Jurgen Philippaerts
2002-04-09 21:23 ` arch/sparc64/kernel/traps.c David S. Miller
2002-04-09 21:47 ` arch/sparc64/kernel/traps.c Jurgen Philippaerts
2002-04-09 22:57 ` arch/sparc64/kernel/traps.c David S. Miller
2002-04-10 13:39 ` arch/sparc64/kernel/traps.c Jurgen Philippaerts
2002-04-11 10:50 ` arch/sparc64/kernel/traps.c Denis Vlasenko
2002-04-11 10:34 ` Jurgen Philippaerts [this message]
2002-04-11 17:53 ` arch/sparc64/kernel/traps.c Denis Vlasenko
2002-04-11 14:08 ` arch/sparc64/kernel/traps.c Jurgen Philippaerts
2002-04-10 8:31 ` arch/sparc64/kernel/traps.c Luigi Genoni
2002-04-10 10:27 ` arch/sparc64/kernel/traps.c Keith Owens
2002-04-10 11:49 ` arch/sparc64/kernel/traps.c Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020411103444.GA7280@sparkie.is.traumatized.org \
--to=jurgen@pophost.eunet.be \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®