Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: Where is the gnu/cygwin GUI Source code debugger? Date: Mon, 12 Jul 2004 09:46:23 -0400 Message-ID: <64F3B586D8A2604780C893B5DAAE0A1624FA32@pauex2ku04.agere.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Williams, Gerald S \(Jerry\)" To: "Richard Heintze" Cc: X-OriginalArrivalTime: 12 Jul 2004 13:46:23.0855 (UTC) FILETIME=[9EF397F0:01C46816] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id i6CDklPx028893 Richard Heintze wrote: > I explicitly downloaded insight seperately and had > troubles with that too, see my earler post. (gdb.exe > started the GUI interface, but it could not load the > source code file -- something to do with stat failing. > chmod 777 test.c did not help). You shouldn't have to download insight separately, since it is part of the gdb package (as Arturus Magi pointed out). As Chris Faylor pointed out, use the command "insight" (assuming it is properly installed). -Jerry -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/