Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: `chain-frame'
Date: Fri, 10 Jan 2003 15:47:00 -0000	[thread overview]
Message-ID: <3E1EEAFD.7060508@redhat.com> (raw)
In-Reply-To: <20030109031217.GA10222@nevyn.them.org>


>> This unwinds to the ``inner most frame''.  Instead of calling 
>> create_new_frame(), get_current_frame() creates this frame and then 
>> unwinds it.
> 
> 
> Oh, er.  Right, I should have understood that by now.  Thank you.

If I was ever granted a wish allowing me to change one (pair) of gdb 
commands, up/down would be it.

>> Oops, yes.  Just:
>> 
>> 	chain-frame:
>> 
>> though I think.
> 
> 
> This'll require playing around with my vocabulary a little to get used
> to it, but I can buy it.  The general action is "unwinding"; looking
> for the "chain" is one mechanism.  I like it.

Er, actually, I've, hopefully, got a beter idea:

	extras-frame

It reflects how the original frame code would use INIT_EXTRA_FRAME_INFO 
during initialization.

Thing is, the phrase `frame chain' is just too useful when describing 
the [er] frame chain (all the frames strung together).

Andrew



  parent reply	other threads:[~2003-01-10 15:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-09  2:11 `chain-frame' Andrew Cagney
2003-01-09  2:38 ` `chain-frame' Daniel Jacobowitz
2003-01-09  3:06   ` `chain-frame' Andrew Cagney
2003-01-09  3:12     ` `chain-frame' Daniel Jacobowitz
2003-01-09 16:04       ` `chain-frame' Andrew Cagney
2003-01-10 15:47       ` Andrew Cagney [this message]
2003-01-10 15:52         ` `chain-frame' Daniel Jacobowitz
2003-01-10 16:18           ` `chain-frame' Andrew Cagney
2003-01-10 16:21             ` `chain-frame' Daniel Jacobowitz
2003-01-10 18:40               ` `chain-frame' 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=3E1EEAFD.7060508@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.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