From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Use of create_new_frame from 'frame'.
Date: Wed, 08 Jul 2015 20:16:00 -0000 [thread overview]
Message-ID: <20150708201613.GD17985@embecosm.com> (raw)
In-Reply-To: <83io9uv3lb.fsf@gnu.org>
* Eli Zaretskii <eliz@gnu.org> [2015-07-08 22:42:08 +0300]:
> > Date: Wed, 8 Jul 2015 18:09:44 +0100
> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> >
> > I wonder then if there's a better way to offer this feature. The two
> > possible choices (other suggestions welcome) are:
> >
> > 1. Create a new command 'create-frame' that takes one or two
> > arguments, and always creates and selects a new frame new frame.
> > The frame command no longer creates new frames.
> >
> > 2. Make 'frame' take an (optional) flag (like 'x', or
> > 'disassemble'), so a user can now say:
> > frame /c STACK-ADDR PC-ADDR
> > in order to create (and select) a new frame. Without the /c flag
> > no new frames are created. With the flag only new frames are
> > created, old frames are not selected.
>
> You could also ask the user for confirmation, when the command is
> going to create a new frame.
That's certainly a possible option. I didn't list it as it does not
in itself solve the problem of different length backtraces preventing
the creation of frames; a backtrace of length 100 means the user can't
create a frame at address 100.
Thanks,
Andrew
prev parent reply other threads:[~2015-07-08 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 17:09 Andrew Burgess
2015-07-08 18:02 ` Pedro Alves
2015-07-08 19:42 ` Eli Zaretskii
2015-07-08 19:46 ` Pedro Alves
2015-07-08 20:06 ` Eli Zaretskii
2015-07-08 20:16 ` Andrew Burgess [this message]
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=20150708201613.GD17985@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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).