From: Elena Zannoni <ezannoni@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Nick Roberts <nick@nick.uklinux.net>,
gdb@sources.redhat.com
Subject: Re: Questions about GDB/MI
Date: Wed, 05 Feb 2003 14:44:00 -0000 [thread overview]
Message-ID: <15937.9267.706792.315945@localhost.redhat.com> (raw)
In-Reply-To: <20030205003347.GB22338@nevyn.them.org>
Daniel Jacobowitz writes:
> On Tue, Feb 04, 2003 at 07:22:34PM -0500, Elena Zannoni wrote:
> > Nick Roberts writes:
> > > My simple program prints out:
> > >
> > > a[0]=0
> > >
> > > shouldn't that be:
> > >
> > > @"a[0]=0"
> > >
> >
> > Don't remember what the status of this is. Look through the bugs
> > database, for open MI bugs. But I see a testcase in the testsuite, and
> > code in the mi directory, so it should work.
>
> That's a nebulous "should". It hasn't been implemented yet.
>
This works with remote targets for SID and redboot. It doesn't work
for native and targets that don't channel the printf's output to gdb.
> >
> > > Annotation uses ^Z^Z to flag things which I guess is not normal output. What
> > > would happen if the program being debugged printed out strings like *stopped
> > > or ^running? These only contain ASCII characters after all.
>
> Once it is implemented, then the program's output would all be escaped.
>
Once it is implemented for natives.
> --
> Daniel Jacobowitz
> MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-05 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 23:32 Nick Roberts
2003-02-05 0:18 ` Elena Zannoni
2003-02-05 0:33 ` Daniel Jacobowitz
2003-02-05 14:44 ` Elena Zannoni [this message]
2003-02-06 0:44 ` Nick Roberts
2003-02-06 15:26 ` Elena Zannoni
2003-02-05 7:23 ` Jim Blandy
2003-02-05 14:45 ` Elena Zannoni
2003-02-09 15:24 ` GDB/MI stream separation 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=15937.9267.706792.315945@localhost.redhat.com \
--to=ezannoni@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=nick@nick.uklinux.net \
/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