This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdbarch_skip_solib_resolver question
- From: "Mark Kettenis" <mark dot kettenis at xs4all dot nl>
- To: "Michael Eager" <eager at eagerm dot com>
- Cc: gdb at sourceware dot org
- Date: Wed, 11 Jan 2012 09:43:42 +0100
- Subject: Re: gdbarch_skip_solib_resolver question
- References: <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.