From: Daniel Jacobowitz <drow@false.org>
To: Nathan Sidwell <nathan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: adjust linux-dp test
Date: Wed, 29 Nov 2006 15:33:00 -0000 [thread overview]
Message-ID: <20061129153311.GC1348@nevyn.them.org> (raw)
In-Reply-To: <456DA7A4.9000709@codesourcery.com>
On Wed, Nov 29, 2006 at 03:30:44PM +0000, Nathan Sidwell wrote:
> Daniel Jacobowitz wrote:
>
> >I think you need to allow newlines in this output anyway; it might wrap
> >printing many parameters of a function. So may as well just relax the
> >error for now.
>
> it'd be easy enough to skip unrecognized lines though. but why would it
> wrap? there's a 'set width 0' to stop gdb wrapping things.
Oh, guess so. I don't really want to add a patch that recognizes that
error message here; the error message is wrong, we really shouldn't be
printing it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-29 15:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 14:58 Nathan Sidwell
2006-11-29 15:08 ` Daniel Jacobowitz
2006-11-29 15:15 ` Nathan Sidwell
2006-11-29 15:24 ` Daniel Jacobowitz
2006-11-29 15:30 ` Nathan Sidwell
2006-11-29 15:33 ` Daniel Jacobowitz [this message]
2006-11-29 15:59 ` Nathan Sidwell
2006-11-29 16:03 ` Daniel Jacobowitz
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=20061129153311.GC1348@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nathan@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