From: Pedro Alves <palves@redhat.com>
To: Michael Eager <eager@eagerm.com>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, gdb@sourceware.org
Subject: Re: gdbarch_skip_solib_resolver question
Date: Wed, 11 Jan 2012 17:13:00 -0000 [thread overview]
Message-ID: <4F0DC326.2090803@redhat.com> (raw)
In-Reply-To: <4F0DC166.2040603@eagerm.com>
On 01/11/2012 05:05 PM, Michael Eager wrote:
> Unless I'm reading the code wrong, I don't think this can ever return
> non-zero. This is called from handle_inferior_event (infrun.c:4754)
> when in_solib_dynsym_resolve_code() is true. This means that the
> pc points to the start of a PLT stub.
That's not the only time in_solib_dynsym_resolve_code returns true,
see svr4_in_dynsym_resolve_code. It returns true as well when the
PC is within the interpreter / dynamic linker's text.
--
Pedro Alves
next prev parent reply other threads:[~2012-01-11 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 20:09 Michael Eager
2012-01-11 8:44 ` Mark Kettenis
2012-01-11 16:24 ` Michael Eager
2012-01-11 17:06 ` Michael Eager
2012-01-11 17:13 ` Pedro Alves [this message]
2012-01-11 17:38 ` Michael Eager
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=4F0DC326.2090803@redhat.com \
--to=palves@redhat.com \
--cc=eager@eagerm.com \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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