This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: mi/2398: newline after stream-record
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 2 Jan 2008 13:08:01 -0000
- Subject: Re: mi/2398: newline after stream-record
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR mi/2398; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: Andrey Batyyev <generatorglukoff@gmail.com>
Cc: gdb-gnats@sourceware.org
Subject: Re: mi/2398: newline after stream-record
Date: Wed, 2 Jan 2008 08:01:35 -0500
On Wed, Jan 02, 2008 at 08:16:45AM +0200, Andrey Batyyev wrote:
> 2008/1/2, Daniel Jacobowitz <drow@false.org>:
> > On Wed, Jan 02, 2008 at 03:45:00AM -0000, generatorglukoff@gmail.com wrote:
> > > In documentation there is no newline after stream-record field, however gdb put it.
> > > For example:
> > >
> > > -exec-run
> > > ^running
> > > (gdb)
> > > &"No executable file specified.\n"
> > > &"Use the \"file\" or \"exec-file\" command.\n"
> > > ^error,msg="No executable file specified.\nUse the \"file\" or \"exec-file\" command."
> > > (gdb)
> >
> > "or a quoted C string (which does not contain an implicit newline)."
> >
> > \n in the string is not an implicit newline, it's an explicit
> > newline. An implicit newline would mean "the end of the string is
> > automatically followed by an additional newline that GDB does not
> > display".
> >
>
> I mean, that by manual correct response must be something like:
>
> &"No executable file specified.\n"&"Use the \"file\" or
> \"exec-file\"^error,msg="No executable file specified.\nUse the
> \"file\" or \"exec-file\" command."
> (gdb)
Oh, I see. I think it's just an error in the manual.
--
Daniel Jacobowitz
CodeSourcery