From: "Mark Kettenis" <mark.kettenis@xs4all.nl>
To: "Michael Eager" <eager@eagerm.com>
Cc: gdb@sourceware.org
Subject: Re: gdbarch_skip_solib_resolver question
Date: Wed, 11 Jan 2012 08:44:00 -0000 [thread overview]
Message-ID: <4e8cbd44794a5d98bc46a882c1379405.squirrel@webmail.xs4all.nl> (raw)
In-Reply-To: <4F0C9AD3.2000807@eagerm.com>
> I noticed that gdbarch_skip_solib_resolver() invokes
> glibc_skip_solib_resolver() on x86, mips, and sh to identify
> that gdb is stepping into _dl_runtime_resolve.
>
> On PowerPC, gdbarch_skip_solib_resolver() always returns a zero.
>
> I don't see any problem with gdb stopping in _dl_runtime_resolve
> or not stepping over the routine.
>
> So, what does this mean? Is calling glibc_skip_solib_resolver()
> optional? Or is the handle_inferior_event() code so convoluted
> or intelligent that it works even when pieces are missing?
>
If I remember correctly, gdbarch_skip_solib_resolver() is just an
optimization. If it returns an address where GDB can set a breakpoint
that gets hit upon return from the dynamic linker. If
gdbarch_skip_solib_resolver() returns zero GDB just single-steps through
the dynamic linker, which works, but is a bit slower.
next prev parent reply other threads:[~2012-01-11 8:44 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 [this message]
2012-01-11 16:24 ` Michael Eager
2012-01-11 17:06 ` Michael Eager
2012-01-11 17:13 ` Pedro Alves
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=4e8cbd44794a5d98bc46a882c1379405.squirrel@webmail.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=eager@eagerm.com \
--cc=gdb@sourceware.org \
/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