This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: debugging a dynamically loaded library
- To: "H . J . Lu" <hjl at lucon dot org>, Kevin Buettner <kevinb at cygnus dot com>
- Subject: Re: debugging a dynamically loaded library
- From: Kevin Buettner <kevinb at cygnus dot com>
- Date: Wed, 5 Sep 2001 23:04:03 -0700
- Cc: Mike Krogh <krogh at ceintl dot com>, gdb at sourceware dot cygnus dot com
- References: <15245.21579.555348.285018@gomer.ceintl.com> <krogh@ceintl.com> <1010829224126.ZM19874@ocotillo.lan> <20010829160725.A25904@lucon.org> <hjl@lucon.org> <1010903225850.ZM1797@ocotillo.lan> <20010905222950.A21097@lucon.org>
On Sep 5, 10:29pm, H . J . Lu wrote:
> 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?
It's always possible that there's a bug elsewhere, but my guess is
that __strtol_internal() is merely the first function in the section
in which case the above entry makes sense to me.
Kevin