From: Marc Khouzam <marc.khouzam@ericsson.com>
To: Daniel Jacobowitz <drow@false.org>,
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" <gdb@sourceware.org>
Subject: RE: GDB GUI
Date: Sat, 07 Nov 2009 11:22:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5158E0215D@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20091106214946.GA22297@caradoc.them.org>
> -----Original Message-----
> From: gdb-owner@sourceware.org
> [mailto:gdb-owner@sourceware.org] On Behalf Of Daniel Jacobowitz
> Sent: November-06-09 4:50 PM
> To: Marco Menegazzi
> Cc: Nick Roberts; Sérgio Durigan Júnior; gdb@sourceware.org
> Subject: Re: GDB GUI
>
> 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.
If you want an example you can look at some Eclipse code.
Below is some information on how to check it out with CVS.
But in case that is too intimidating, you can look at the code on the web.
Here are the interesting files:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/command/output/?root=Tools_Project
look for MIParser.java
In fact, here is the link to the MIParser.java:
http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/dsf-gdb/org.eclipse.cdt.dsf.gdb/src/org/eclipse/cdt/dsf/mi/service/command/output/MIParser.java?revision=1.1&root=Tools_Project&view=markup
To check out using CVS:
pserver:anonymous@proxy.eclipse.org:80
under
/cvsroot/tools
under
HEAD/org.eclipse.cdt/dsf-gdb
get the plugin
org.eclipse.cdt.dsf.gdb
and look at
MIParser.java
Marc
prev parent reply other threads:[~2009-11-07 1:14 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
2009-11-07 11:22 ` Marc Khouzam [this message]
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=F7CE05678329534C957159168FA70DEC5158E0215D@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=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