From: Quality Quorum <qqi@theworld.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
"Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: (remote) hellishly slow single stepping over library calls
Date: Fri, 16 May 2003 23:10:00 -0000 [thread overview]
Message-ID: <Pine.SGI.4.40.0305161907570.4512842-100000@shell01.TheWorld.com> (raw)
In-Reply-To: <078501c31be6$52622e60$0202040a@catdog>
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
next prev parent reply other threads:[~2003-05-16 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-16 18:25 Kris Warkentin
2003-05-16 18:50 ` Theodore A. Roth
2003-05-16 18:57 ` Kris Warkentin
2003-05-16 19:15 ` Quality Quorum
2003-05-16 19:24 ` Kris Warkentin
2003-05-16 19:29 ` Daniel Jacobowitz
2003-05-16 20:04 ` Kris Warkentin
2003-05-16 23:10 ` Quality Quorum [this message]
2003-05-17 3:39 ` Andrew Cagney
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=Pine.SGI.4.40.0305161907570.4512842-100000@shell01.TheWorld.com \
--to=qqi@theworld.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).