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
> > 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?
cheers,
Kris