From: Eli Zaretskii <eliz@elta.co.il>
To: Jim Blandy <jimb@redhat.com>
Cc: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] frame_id_unwind
Date: Mon, 29 Mar 2004 06:47:00 -0000 [thread overview]
Message-ID: <uvfkojgin.fsf@elta.co.il> (raw)
In-Reply-To: <vt24qs8n8gz.fsf@zenia.home> (message from Jim Blandy on 28 Mar 2004 13:15:56 -0500)
> From: Jim Blandy <jimb@redhat.com>
> Date: 28 Mar 2004 13:15:56 -0500
>
> Wouldn't things work better if we moved the decision about where to
> stop displaying the stack into user interface code (I don't know if
> there's any place shared by cli and mi, but perhaps one could be
> created), and left get_prev_frame as a pure stack-traversal function?
Yes, I think it would be a good idea to separate the decision of
whether to display a frame from the code that traverses the funcall
stack.
next prev parent reply other threads:[~2004-03-29 6:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 14:26 Andrew Cagney
2004-03-28 18:16 ` Jim Blandy
2004-03-28 22:31 ` Andrew Cagney
2004-03-29 6:47 ` Eli Zaretskii [this message]
2004-03-31 19:42 ` 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=uvfkojgin.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=cagney@gnu.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@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