From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: Nick Roberts <nickrob@snap.net.nz>, gdb-patches@sources.redhat.com
Subject: Re: MI: Another -var-update bug? [PATCH]
Date: Fri, 05 Jan 2007 15:10:00 -0000 [thread overview]
Message-ID: <20070105150954.GE24554@nevyn.them.org> (raw)
In-Reply-To: <200701051210.09186.ghost@cs.msu.su>
On Fri, Jan 05, 2007 at 12:10:09PM +0300, Vladimir Prus wrote:
> On Friday 05 January 2007 02:59, Nick Roberts wrote:
> > > This patch introduces this for me:
> > >
> > > FAIL: gdb.mi/mi-var-cp.exp: update RX (3)
> > >
> > > Do you get this failure to? If yes, can you please fix it?
> > > If no, let me know and I'll investigate.
> >
> > I don't get this failure.
>
> I suppose you've got some different version of gcc. I'll take a look.
I don't see the failure either.
> > Yes, it looks like the call to select_frame is not needed when the variable is
> > out of scope.
>
> Good. Do we have a rule in place that small fixes to one's most recent commit that
> seem obvious to you can be just committed? If yes, can you change this?
We don't have such a rule - but this would be an obvious change anyway,
in my opinion.
> > Daniel also suggested removing the call to reinit_frame_cache.
>
> I think that would be great as a separate patch.
Yes, I've been meaning to do it. Wasn't it part of a patch of mine you
reposted recently?
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-01-05 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 11:09 MI: Another -var-update bug? Nick Roberts
2006-12-13 6:32 ` MI: Another -var-update bug? [PATCH] Nick Roberts
2006-12-30 15:06 ` Daniel Jacobowitz
2006-12-30 22:43 ` Nick Roberts
2006-12-31 2:19 ` Daniel Jacobowitz
2007-01-01 16:24 ` Daniel Jacobowitz
2007-01-01 22:13 ` Nick Roberts
2007-01-04 18:51 ` Vladimir Prus
2007-01-04 19:43 ` Nick Roberts
2007-01-04 18:49 ` Vladimir Prus
2007-01-04 23:59 ` Nick Roberts
2007-01-05 9:10 ` Vladimir Prus
2007-01-05 15:10 ` Daniel Jacobowitz [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=20070105150954.GE24554@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=ghost@cs.msu.su \
--cc=nickrob@snap.net.nz \
/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