From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Yao Qi <yao@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Don't allow setting register in non-innermost frame
Date: Thu, 23 Aug 2012 16:25:00 -0000 [thread overview]
Message-ID: <87hartpodt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22SGp-9TaoA3rNi_PJordCuv_bjwFQZiHvfjktHx3Y_krA@mail.gmail.com> (Doug Evans's message of "Mon, 20 Aug 2012 13:19:36 -0700")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> fwiw, I've been able to work around corrupt, or otherwise not
Doug> completely useful, core files by setting registers in non-innermost
Doug> frames.
Doug> Granted, I knew what was happening underneath the covers, so to speak,
Doug> and I could have done things differently, but I like this capability.
It does seem like a useful power user tool.
I'm swayed by this argument.
Doug> I *could* accept a warning when changing a register in a non-innermost
Doug> frame, fwiw.
That would be ok by me.
Tom
next prev parent reply other threads:[~2012-08-23 16:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 2:21 Yao Qi
2012-08-20 20:19 ` Doug Evans
2012-08-21 3:27 ` Yao Qi
2012-08-23 16:25 ` Tom Tromey [this message]
2012-08-29 9:51 ` Yao Qi
2012-09-04 22:37 ` dje
2012-09-07 10:01 ` Yao Qi
2012-09-07 10:11 ` Eli Zaretskii
2012-09-07 10:21 ` Yao Qi
2012-09-07 11:27 ` Eli Zaretskii
2012-09-07 13:14 ` Yao Qi
2012-09-07 14:32 ` Eli Zaretskii
2012-09-07 16:46 ` Jan Kratochvil
2012-09-09 2:31 ` Yao Qi
2012-09-10 2:02 ` Yao Qi
2012-09-10 7:47 ` Jan Kratochvil
2012-09-10 19:43 ` Jan Kratochvil
2012-09-11 17:12 ` Tom Tromey
2012-09-11 17:19 ` Jan Kratochvil
2012-09-11 17:23 ` Tom Tromey
2012-09-12 0:51 ` Yao Qi
2012-09-12 13:19 ` Jan Kratochvil
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=87hartpodt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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