This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: (remote) hellishly slow single stepping over library calls
- From: Quality Quorum <qqi at theworld dot com>
- To: Kris Warkentin <kewarken at qnx dot com>
- Cc: Daniel Jacobowitz <drow at mvista dot com>, "Gdb at Sources dot Redhat dot Com" <gdb at sources dot redhat dot com>
- Date: Fri, 16 May 2003 19:10:21 -0400
- Subject: Re: (remote) hellishly slow single stepping over library calls
On Fri, 16 May 2003, Kris Warkentin wrote:
> > > I'll look into implementing that sort of thing on our end.
> >
> > It should be pretty straightforward to do. When you get the right
> > registers, it's quite effective, too.
>
> I took a look at our notify message and it already has space for various
> registers in it depending on what the notification is for (ie. single step,
> break, etc.) I should be able to stuff them on the target end and supply
> them every time gdb stops. Other than empirically, where can I discover
> what registers are needed for various targets? I'm thinking IP for everyone
> but are some going to want stack and frame pointers as well?
I suppose that a program counter, a frame pointer and a stack pointer will
be enough. It is easy to test, if gdb needs more resiters it will pull
them all in.
>
> cheers,
>
> Kris
>
Thanks,
Aleksey