From: Jim Ingham <jingham@apple.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: [multi-arch] The frame as the global parameter (long, important)
Date: Mon, 26 Feb 2001 18:14:00 -0000 [thread overview]
Message-ID: <200102270214.SAA19200@scv1.apple.com> (raw)
In-Reply-To: <3A9AF421.A0D723D0@cygnus.com>
Andrew,
>
>
>> So, yeah, it seems like this should work, provided you make sure you
>> don't assume that there is only one valid result of a backtrace, and
>> make switching the order fairly easy...
>
> Hmm, GDB currently assumes that, given a frame, there is only one
> possible next frame. I'll be leaving that assumption alone :-)
I don't think this is really that much of a problem. In the scheme I
was sketching, given an ordering of the "frame recognizers" the previous
frame will always be unique. But if you switch the ordering, then the
previous frame will change. You will need this in your RPC example too,
since I would definitely want the ability to turn off tracing across the
RPC, and in this case the frame ordering will change as well.
This is a pretty heavyweight thing to do, however, so it is probably
safe to blow away the frame cache and start all over if you do this...
So as long as cleaning up all your state and starting over is easy to
do, then this will fall out.
Jim
--
Jim Ingham jingham@apple.com
Developer Tools - gdb
Apple Computer
next prev parent reply other threads:[~2001-02-26 18:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <983058218.3463.ezmlm@sources.redhat.com>
2001-02-26 10:17 ` Jim Ingham
2001-02-26 13:16 ` Nick Duffek
2001-02-26 13:27 ` Jim Ingham
2001-02-26 13:28 ` Per Bothner
2001-02-26 13:50 ` Andrew Cagney
2001-02-26 14:52 ` Jim Ingham
2001-02-26 16:28 ` Andrew Cagney
2001-02-26 18:14 ` Jim Ingham [this message]
2001-02-23 16:34 Andrew Cagney
2001-02-26 13:12 ` Nick Duffek
2001-02-26 13:53 ` Kevin Buettner
2001-02-26 15:27 ` Nick Duffek
2001-02-26 15:55 ` Kevin Buettner
2001-02-26 14:42 ` Andrew Cagney
2001-02-26 13:44 ` Kevin Buettner
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=200102270214.SAA19200@scv1.apple.com \
--to=jingham@apple.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.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