From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11350 invoked by alias); 13 Jan 2003 15:39:53 -0000 Mailing-List: contact insight-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sources.redhat.com Received: (qmail 11343 invoked from network); 13 Jan 2003 15:39:52 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by 209.249.29.67 with SMTP; 13 Jan 2003 15:39:52 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id h0DFBYB14090 for ; Mon, 13 Jan 2003 10:11:34 -0500 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h0DFdea28360; Mon, 13 Jan 2003 10:39:40 -0500 Received: from [150.1.200.14] (vpn50-46.rdu.redhat.com [172.16.50.46]) by pobox.corp.redhat.com (8.11.6/8.11.6) with ESMTP id h0DFddS22829; Mon, 13 Jan 2003 10:39:39 -0500 Subject: Re: Insight debugger question From: Keith Seitz To: Chris Dye Cc: "insight@sources.redhat.com" In-Reply-To: <20030113042509.5344.qmail@web21201.mail.yahoo.com> References: <20030113042509.5344.qmail@web21201.mail.yahoo.com> Content-Type: text/plain Organization: Message-Id: <1042472479.1457.21.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Mon, 13 Jan 2003 15:39:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q1/txt/msg00016.txt.bz2 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++? [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.] >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