This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: How to tell gdb about dlls using remote protocol
- From: Daniel Jacobowitz <drow at false dot org>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: brobecker at adacore dot com, Wiljan dot Derks at zonnet dot nl, gdb at sourceware dot org
- Date: Wed, 7 Feb 2007 17:16:44 -0500
- Subject: Re: How to tell gdb about dlls using remote protocol
- References: <003f01c7457c$0f2d8090$9600000a@kamer> <20070131223113.GA15122@nevyn.them.org> <20070201175311.GG17864@adacore.com> <200702072214.l17MER45023107@brahms.sibelius.xs4all.nl>
On Wed, Feb 07, 2007 at 11:14:27PM +0100, Mark Kettenis wrote:
> I think this diff makes sense. However, I'm pretty sure there are
> Linux systems out there where this will make things worse :(. In
> particular, on kernels with a vsyscall page buit without the stub
> shared library for that page, this change will systematically skip a
> frame. And that frame is quite crucial since it is the frame for the
> libc system call stub, so it will be hard for a user to find out in
> what system call the program is blocked on.
>
> I have no idea though how many people are still runing those kernels.
> That number might be very low enough for us not to care.
For what it's worth, I think it is. And, if it isn't, it would be
straightforward to add a custom frame sniffer to i386-linux-tdep.c
to recognize that case. I don't know what the affected versions
are, though.
--
Daniel Jacobowitz
CodeSourcery