From: Nick Roberts <nick@nick.uklinux.net>
To: gdb@sources.redhat.com
Subject: Questions about GDB/MI
Date: Tue, 04 Feb 2003 23:32:00 -0000 [thread overview]
Message-ID: <15936.19654.642542.951794@nick.uklinux.net> (raw)
I'm trying to get my head round GDB/MI and have a few simple/dumb questions:
Simple example in info pages:
You say:
> -> -stop
> <- (gdb)
>
> and later:
>
> <- *stop,reason="stop",address="0x123",source="a.c:123"
> <- (gdb)
I get:
-> -stop
<- ^error,msg="Undefined MI command: stop"
<- (gdb)
You say:
> -> print 1+2
> <- ~3\n
> <- (gdb)
I get:
-> print 1+2
<- &"print 1+2\n"
<- ~"$1 = 3"
<- ~"\n"
<- ^done
<- (gdb)
Running a simple program, I get a sequence like:
-> -exec-next
<- ^running
<- (gdb)
<- *stopped,reason="end-stepping-range",thread-id="0",frame={addr="0x08048578",func="main",args=[],file="myprog.c",line="18"}
<- (gdb)
According to the GDB/MI Output Syntax shouldn't that be:
-> -exec-next
<- ^running
<- *stopped,reason="end-stepping-range",thread-id="0",frame={addr="0x08048578",func="main",args=[],file="myprog.c",line="18"}
<- (gdb)
i.e isn't that one (gdb) too many?
My simple program prints out:
a[0]=0
shouldn't that be:
@"a[0]=0"
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.
And one question about the repository. I've checked out as Elena advised. I've
got the interp branch but every time I use `cvs update' in src, even without
the -d option it keeps on trying to give me other directories like binutils. I
have to go into gdb and do `cvs update' there where I just get gdbtk but I'm
worried that then I might be missing other files that I need..
Nick
next reply other threads:[~2003-02-04 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 23:32 Nick Roberts [this message]
2003-02-05 0:18 ` Elena Zannoni
2003-02-05 0:33 ` Daniel Jacobowitz
2003-02-05 14:44 ` Elena Zannoni
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=15936.19654.642542.951794@nick.uklinux.net \
--to=nick@nick.uklinux.net \
--cc=gdb@sources.redhat.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