From: Keith Seitz <keiths@redhat.com>
To: Chris Dye <dreamcastuser99@yahoo.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: Insight debugger question
Date: Mon, 13 Jan 2003 15:39:00 -0000 [thread overview]
Message-ID: <1042472479.1457.21.camel@lindt.uglyboxes.com> (raw)
In-Reply-To: <20030113042509.5344.qmail@web21201.mail.yahoo.com>
On Sun, 2003-01-12 at 20:25, Chris Dye wrote:
> I have been using Dev C++ 5 and I don't understand how
> to use the debugger...I've heard that the Insight
> debugger is better than the one that comes with Dev
> C++, but the thing is that BloodShed said that it
> won't work with the new versions of Dev C++ for some
> reason. Will there be a updated version of Insight
> Debugger that will work with Dev C++?
<sour cherries>
[Omit venemous leaching accusations about Bloodshed and other companies
that have made me they're free technical support. Thanks a lot. I
appreciate all the "help" and incentive I get from you all.]
</sour cherries>
From the Bloodshed web page, it says that it uses gcc. Therefore, it
must use gdb, and if it uses gdb, it can use Insight, since Insight is
simply built on top of gdb (unlike all the other GUI debuggers for gdb
out there). In fact, I see from the packages page, they _are_
distributing a binary version of Insight. [Hmm.. no mention of sources,
though. I guess I should persue this and see if they are violating the
GPL.]
Perhaps what they are referring to is the fact that GDB doesn't work
very well with GCC 3.2's new C++ debug ABIs? This is a well known
problem which has nothing to do with Insight, of course. The GDB folks
are trying to fix this, but it will take time. GCC developers outnumber
GDB developers at least 20:1.
Keith
prev parent reply other threads:[~2003-01-13 15:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 4:25 Chris Dye
2003-01-13 15:39 ` Keith Seitz [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=1042472479.1457.21.camel@lindt.uglyboxes.com \
--to=keiths@redhat.com \
--cc=dreamcastuser99@yahoo.com \
--cc=insight@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).