From: Kevin Buettner <kevinb@cygnus.com>
To: "H . J . Lu" <hjl@lucon.org>, 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 23:05:00 -0000 [thread overview]
Message-ID: <1010906060403.ZM6589@ocotillo.lan> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2001-09-05 23:05 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
2001-09-05 23:05 ` Kevin Buettner [this message]
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=1010906060403.ZM6589@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--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