Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>, 	Denis PILAT <denis.pilat@st.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] -thread-select double print stack frame
Date: Wed, 28 Mar 2007 11:43:00 -0000	[thread overview]
Message-ID: <20070328114256.GA2688@caradoc.them.org> (raw)
In-Reply-To: <460A2681.30700@st.com> <17930.715.767042.438147@farnswood.snap.net.nz>

On Wed, Mar 28, 2007 at 05:53:15PM +1200, Nick Roberts wrote:
> I was looking specifically at this clause in print_source_lines_base:
> 
>   if (desc < 0)

Right, that's where it comes from.

> I think this code may only be reached when there is duplicated MI output.

I don't know.  Some of the source-related commands may also call
print_source_lines, in which case they'll get here too - without a
frame printout.

>  > This does make me wonder about the patch though.  Denis, could you
>  > hold off on committing it?  Which duplicate copy are you eliminating?
>  > Maybe we should diff two testsuite runs to see what else changes.
> 
> No, I think this change is alright (I haven't run the testsuite though.).

You're right, anyway.  That's what I get for reviewing patches while
I'm so tired.  I was worried that the copy inside the frame={} tuple
was being eliminated by this change, but that's definitely not what
happens.  Only -thread-select of everything in our testsuite changed.

On Wed, Mar 28, 2007 at 10:25:37AM +0200, Denis PILAT wrote:
> I do run the testsuite on i386-linux native target, no regression at all.
> Can I commit or not ?

Yes, go ahead.  Thanks.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2007-03-28 11:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 13:48 Denis PILAT
2007-03-20  0:57 ` Nick Roberts
2007-03-26 13:19   ` Denis PILAT
2007-03-27 19:33     ` Daniel Jacobowitz
2007-03-27 21:42       ` Nick Roberts
2007-03-28  2:11         ` Daniel Jacobowitz
2007-03-28  5:56           ` Nick Roberts
2007-03-28  8:26             ` Denis PILAT
2007-03-28 11:43         ` Daniel Jacobowitz [this message]
2007-03-29  7:45           ` Denis PILAT

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=20070328114256.GA2688@caradoc.them.org \
    --to=drow@false.org \
    --cc=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    --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