Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Regression in exec.c (print_section_info) ?
Date: Tue, 29 Apr 2008 14:29:00 -0000	[thread overview]
Message-ID: <18454.51085.276103.301144@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080429030510.GA28505@adacore.com>

 > > This works for me, e.g. with "info target" but perhaps there is a bigger
 > > picture and this line was removed for another reason.
 > 
 > I reviewed the history of the change, and I think it was an oversight.
 > The change that removed the newline was meant to get rid of some uses
 > of current_gdbarch, no more.
 > 
 > Could you test the attached? I think it's generally better for
 > internationalization to have one string rather than put together several
 > string blocks. I doubt it would make much difference in this case, but
 > might as well.
 >
 > I would also like to see a new test if we don't already have one to
 > prevent this type of regression in the future. 

It's easy to create a test for this specific case but I think it's very hard to
test the exact format of all CLI output in general, and probably not worth the
effort.  The next regression will likely occur elsewhere.

 >                                                 Please confirm that
 > you did run the patch against the testcase on at least one architecture.

I only have one architecture: my old PC.  I get the same testsuite results
with and without this change (After adding the semi-colon missing in your
patch.).

 > One last thing: You also forgot to provide a ChangeLog entry. 

I didn't really think of it as a patch, I was just trying to draw attention to
the regression.

 >                                                               But *thank
 > you* for sending a unified diff - I just can't read context diffs!

Actually it was a context diff - so you can read them!  They just look similar
when lines are added.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-04-29  7:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28  8:38 Nick Roberts
2008-04-29  7:01 ` Joel Brobecker
2008-04-29 14:29   ` Nick Roberts [this message]
2008-05-01 18:07     ` Joel Brobecker
2008-05-02  1:05       ` Nick Roberts
2008-05-02  5:19         ` Joel Brobecker
2008-05-02 22:29         ` Michael Snyder
2008-05-04  8:34           ` Nick Roberts

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=18454.51085.276103.301144@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=brobecker@adacore.com \
    --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