From: "H . J . Lu" <hjl@lucon.org>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: Mike Krogh <krogh@ceintl.com>, gdb@sourceware.cygnus.com
Subject: Re: debugging a dynamically loaded library
Date: Wed, 05 Sep 2001 22:29:00 -0000 [thread overview]
Message-ID: <20010905222950.A21097@lucon.org> (raw)
In-Reply-To: <1010903225850.ZM1797@ocotillo.lan>
On Mon, Sep 03, 2001 at 03:58:50PM -0700, Kevin Buettner wrote:
> On Aug 29, 4:07pm, H . J . Lu wrote:
>
> > > (gdb) b main.c:23
> > > Breakpoint 1 at 0x80487fc: file main.c, line 23.
> > > (gdb) r
> > > Starting program: /home/kev/ctests/dynlib/main
> > >
> > > Breakpoint 1, main (argc=1, argv=0xbffffa2c) at main.c:23
> > > 23 init = dlsym(handle, "dso_init");
> > > (gdb) b dso_init
> > > Breakpoint 2 at 0x400188a2: file dso.c, line 10.
> >
> > For some reason, it doesn't work for me:
> >
> > GNU gdb 2001-08-29-cvs (MI_OUT)
> > ....
> > (gdb) b main.c:23
> > Breakpoint 1 at 0x8048820: file main.c, line 23.
> > (gdb) r
> > Starting program: /home/hjl/bugs/gdb/dlopen/main
> >
> > Breakpoint 1, main (argc=1, argv=0xbffff804) at main.c:23
> > 23 init = dlsym(handle, "dso_init");
> > (gdb) b dso_init
> > Cannot access memory at address 0x123
> > (gdb) p dso_init
> > $1 = {<text variable, no debug info>} 0x40017800 <dso_init>
> > (gdb) info shared
> > >From To Syms Read Shared Object Library
> > 0x400281d0 0x40028fc0 Yes /lib/libdl.so.2
> > 0x40047400 0x40147080 Yes /lib/i686/libc.so.6
> > 0x40001eb0 0x40012f20 Yes /lib/ld-linux.so.2
> > 0x400176d0 0x400178b0 Yes ./dso.so
> >
> > I am using glibc 2.2.4 on x86. It seems that gdb doesn't add the base
> > address of ./dso.so.
>
> H. J.,
>
> Could you try
>
> http://sources.redhat.com/ml/gdb-patches/2001-09/msg00003.html
>
> and let me know if it fixes the above problem?
>
I just came back from a trip. I will give it try tomorrow. I know there
was at least one gcc bug, which generated bogus debug code for glibc.
I am wondering if
1327 FUN 0 36 00000000 31372 __strtol_internal:F(0,3)
is a valid stab entry. It it is valid, why does it trigger the
SOFUN_ADDRESS_MAYBE_MISSING code in gdb. Is that possible a linker
or assembler bug?
H.J.
next prev parent reply other threads:[~2001-09-05 22:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-29 13:45 Mike Krogh
2001-08-29 15:41 ` Kevin Buettner
2001-08-29 16:07 ` H . J . Lu
2001-08-29 16:59 ` Kevin Buettner
2001-09-03 15:58 ` Kevin Buettner
2001-09-05 22:29 ` H . J . Lu [this message]
2001-09-05 23:05 ` Kevin Buettner
2001-09-06 10:25 ` H . J . Lu
2001-09-18 14:11 ` Mike Krogh
2001-09-18 14:54 ` Kevin Buettner
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=20010905222950.A21097@lucon.org \
--to=hjl@lucon.org \
--cc=gdb@sourceware.cygnus.com \
--cc=kevinb@cygnus.com \
--cc=krogh@ceintl.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