Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Marco Menegazzi <mene.thebear@gmail.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>,
	gdb@sourceware.org
Subject: Re: GDB GUI
Date: Fri, 06 Nov 2009 16:41:00 -0000	[thread overview]
Message-ID: <3FD374F3-B19F-4764-B85D-4A8CC85816F1@gmail.com> (raw)
In-Reply-To: <19186.34927.781254.301460@totara.tehura.co.nz>


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.



Il giorno 05/nov/2009, alle ore 09.10, Nick Roberts ha scritto:

>>                 ... but then I ask myself why to use gdb/mi that
>> returns a more complex output instead of calling directly gdb and
>> parse the stout to get what I want?
>
> Because, over time, normal GDB output is likely to change in a way  
> that will
> break your parser.  In contrast, GDB/MI output shouldn't change in  
> unexpected
> ways.


  reply	other threads:[~2009-11-06 10:56 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 [this message]
2009-11-07  6:58         ` Nick Roberts
2009-11-07 10:20         ` Daniel Jacobowitz
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=3FD374F3-B19F-4764-B85D-4A8CC85816F1@gmail.com \
    --to=mene.thebear@gmail.com \
    --cc=gdb@sourceware.org \
    --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