Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Amit S. Kale" <akale@veritas.com>
To: sjhill@cotw.com
Cc: binutils@sources.redhat.com, gdb@sourceware.cygnus.com,
	linux-mips@oss.sgi.com
Subject: Re: Continued MIPS kernel debugging symbols problem...
Date: Thu, 20 Sep 2001 05:21:00 -0000	[thread overview]
Message-ID: <3BA9DC21.6E5FE0FA@veritas.com> (raw)
In-Reply-To: <3BA16CAA.6B4DF4A1@cotw.com>

Hi,

If you are debugging linux kernel modules, you may find
the loadmodule.sh script from http://kgdb.sourceforge.net/
useful to get a gdb script to load module object files.

"Steven J. Hill" wrote:
> 
> Greetings.
> 
> I have tried everything I can to get Linux kernel debugging
> symbols to work properly. I apologize for posting to so
> many lists too, but I really need to get this working. I
> traded a few emails with HJ Lu and he referred me to the
> following messages/threads:
> 
>    http://sources.redhat.com/ml/gdb/2001-08/msg00053.html
>    http://sources.redhat.com/ml/gdb/2001-08/msg00079.html
>    http://sources.redhat.com/ml/gdb/2001-08/msg00084.html
> 
> I did read them a few times and it appears that all the
> necessary changes are in the current gdb and insight CVS
> repositories. I checked out the latest sources a half
> hour ago and compiled both gdb and insight using the
> configuration line:
> 
>     configure --prefix=/opt/tools --target=mipsel-linux-elf
> 
> since my target is a NEC 5432 running in LE mode. I had
> also tried 'mips-linux-elf' targets earlier in the day
> with no difference. I am still getting the following
> mismatch in symbols:
> 
> --------------------------------------------------------------------
> (gdb) target remote /dev/ttyS1
> Remote debugging using /dev/ttyS1
> 0x80012828 in breakinst () at af_packet.c:1879
> 1879            sock_unregister(PF_PACKET);
> (gdb) bt
> #0  0x80012828 in breakinst () at af_packet.c:1879
> #1  0x8001a0d4 in sys_create_module (name_user=0x10001dc8 "cfi_probe",
>     size=8176) at module.c:305
> (gdb) c
> Continuing.
> --------------------------------------------------------------------
> 
> I compiled my kernel with a toolchain that used the following
> versions of tools:
> 
>     binutils-2.11.90.0.31 (HJLu patches applied)
>     gcc-3.0.1 (stock)
>     glibc-2.2.3 (minor build patches)
> 
> Things are still not working and I would greatly appreciate some
> direction. I've blown a whole day this and am a bit frazzled.
> Thanks a bunch in advance.
> 
> -Steve
> 
> --
>  Steven J. Hill - Embedded SW Engineer

-- 
Amit Kale
Veritas Software India ( http://www.veritasindia.com/ )


      parent reply	other threads:[~2001-09-20  5:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-13 19:43 Steven J. Hill
2001-09-13 21:28 ` Daniel Jacobowitz
2001-09-14  8:07 ` H . J . Lu
2001-09-20  5:21 ` Amit S. Kale [this message]

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=3BA9DC21.6E5FE0FA@veritas.com \
    --to=akale@veritas.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=sjhill@cotw.com \
    /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