From: Tom Tromey <tromey@redhat.com>
To: RT <mfoc73@dsl.pipex.com>
Cc: "'Atul Talesara'" <atul.talesara@nevisnetworks.com>,
"'Hareesh Nagarajan'" <hnagaraj@cs.uic.edu>,
"'GDB'" <gdb@sources.redhat.com>
Subject: Re: Is it possible to save breakpoints to a file?
Date: Sat, 12 Mar 2005 19:39:00 -0000 [thread overview]
Message-ID: <m38y4s4pxn.fsf@localhost.localdomain> (raw)
In-Reply-To: <4232D267.10303@dsl.pipex.com>
>>>>> "RT" == RT <mfoc73@dsl.pipex.com> writes:
RT> I haven't looked at this in detail. I suspect the problem is that
RT> Insight is no longer actively maintained, and so it's difficult to get
RT> a version of insight that uses the current gdb.
You can still build insight out of cvs. It will then use the current
gdb.
RT> A trivial licensing problem has lead to gdb having no
RT> usable GUI (that I know of, anyway; and I've used both ddd and
RT> insight).
There are actually quite a few gdb UIs, in addition to Insight and
DDD. Maybe MI made it too easy to write gdb UIs :-)
There's one written in Ada whose name I forget.
Eclipse also comes with a gdb GUI. (The Eclipse one is interesting
because, AIUI, it saves breakpoints more intelligently, as markers in
your source.)
Apple also has one in their IDE, but I know little about it.
Finally, Anjuta[1] has one and KDevelop[2] has one.
I haven't used most of these, and whether they meet your "usable"
qualification is subjective...
Tom
[1] http://anjuta.sourceforge.net/
[2] http://www.kdevelop.org/
next prev parent reply other threads:[~2005-03-12 19:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 10:52 Atul Talesara
2005-03-10 15:08 ` Kris Warkentin
2005-03-10 15:52 ` Dave Korn
2005-03-10 16:08 ` RT
2005-03-11 1:28 ` Tom Tromey
2005-03-12 11:29 ` RT
2005-03-12 11:58 ` Russell Shaw
2005-03-12 12:13 ` RT
2005-03-12 19:39 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-13 5:03 Paul Schlie
2005-03-10 7:07 Hareesh Nagarajan
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=m38y4s4pxn.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=atul.talesara@nevisnetworks.com \
--cc=gdb@sources.redhat.com \
--cc=hnagaraj@cs.uic.edu \
--cc=mfoc73@dsl.pipex.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