From: Jim Ingham <jingham@apple.com>
To: gdb@sources.redhat.com
Subject: Re: dbg MI help required !
Date: Sat, 21 Jul 2001 10:37:00 -0000 [thread overview]
Message-ID: <300811A9-7DFF-11D5-AD8A-000A277A8808@> (raw)
In-Reply-To: <995730792.22864.ezmlm@sources.redhat.com>
Mickael,
The configure option is:
configure --enable-gdbmi=yes
As an aside, it is a lot more convenient to build the gdb tree in a tree
parallel to the sources. Since the configure process generates c-files,
makes links, etc, it is good not to mess up your source tree with
them... I usually have:
source/configure
source/gdb
source/bfd
source/readline
...
then parallel to this make a directory
build/
then cd into build and do:
../source/configure --enable-gdbmi=yes
Anyway, once you have a gdb built with the mi enabled, then you do:
gdb -i mi
Hope this helps,
Jim
>
> Hi there!
> I am trying to figure out how to use MI and what it is for and to be
> honest i
> am not getting anywhere.
> first i made a native solaris gdb with the following command:
> ./configure --with-gdb-interpreter=mi
> I ran make after and gdb was built but none of the c files in the mi
> directory
> were compiled.
>
> So what do i do next?
> i thought mi would be a library and gdbmi would need that library in
> order to
> support the tidy textual output that mi if i understand properly is
> supposed to
> achieve.
>
> How do i make get gdbmi ?
>
>
> cheers mickael
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
Jim Ingham
jingham@apple.com
Developer Tools - gdb
next parent reply other threads:[~2001-07-21 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <995730792.22864.ezmlm@sources.redhat.com>
2001-07-21 10:37 ` Jim Ingham [this message]
2001-07-23 10:35 ` Andrew Cagney
2001-07-20 8:27 Mickael Gicquaire
2001-07-23 14:17 ` Andrew Cagney
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=300811A9-7DFF-11D5-AD8A-000A277A8808@ \
--to=jingham@apple.com \
--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