From: Daniel Jacobowitz <drow@false.org>
To: Marco Menegazzi <mene.thebear@gmail.com>
Cc: "Nick Roberts" <nickrob@snap.net.nz>,
"Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>,
gdb@sourceware.org
Subject: Re: GDB GUI
Date: Sat, 07 Nov 2009 10:20:00 -0000 [thread overview]
Message-ID: <20091106214946.GA22297@caradoc.them.org> (raw)
In-Reply-To: <3FD374F3-B19F-4764-B85D-4A8CC85816F1@gmail.com>
On Fri, Nov 06, 2009 at 11:59:10AM +0100, Marco Menegazzi wrote:
>
> So if I am not interested in future developements of gdb, because I
> am not working on a gdb frontend but I only need to use gdb under my
> graphical application, could it be useful to interact with gdb
> instead of gdb/mi ? It is just a question to understand if I really
> need to use gdb-mi in my case ...
> Thank you all for the answers.
I really strongly recommend you use GDB/MI.
It's a little trickier to get started, because you're not already
familiar with exactly how GDB/MI looks; you probably know what the GDB
CLI looks like. But the GDB CLI is unpredictable and guaranteed to
generate output you can't parse. It changes between releases, between
systems, and more.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-11-06 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 10:57 Marco Menegazzi
2009-11-02 16:36 ` Sérgio Durigan Júnior
2009-11-04 14:30 ` Marco Menegazzi
2009-11-04 14:36 ` André Pönitz
2009-11-04 15:02 ` Vladimir Prus
2009-11-04 20:06 ` Sérgio Durigan Júnior
2009-11-04 20:15 ` Joel Brobecker
2009-11-05 8:10 ` Nick Roberts
2009-11-06 16:41 ` Marco Menegazzi
2009-11-07 6:58 ` Nick Roberts
2009-11-07 10:20 ` Daniel Jacobowitz [this message]
2009-11-07 11:22 ` Marc Khouzam
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=20091106214946.GA22297@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=mene.thebear@gmail.com \
--cc=nickrob@snap.net.nz \
--cc=sergiodj@linux.vnet.ibm.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