From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25444 invoked by alias); 23 Jan 2006 07:27:59 -0000 Received: (qmail 25436 invoked by uid 22791); 23 Jan 2006 07:27:59 -0000 X-Spam-Check-By: sourceware.org Received: from ylpvm29-ext.prodigy.net (HELO ylpvm29.prodigy.net) (207.115.57.60) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 23 Jan 2006 07:27:57 +0000 Received: from pimout3-ext.prodigy.net (pimout3-int.prodigy.net [207.115.4.218]) by ylpvm29.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k0N7Rmrk029034 for ; Mon, 23 Jan 2006 02:27:48 -0500 X-ORBL: [69.226.254.227] Received: from [192.168.1.4] (adsl-69-226-254-227.dsl.pltn13.pacbell.net [69.226.254.227]) by pimout3-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k0N7Rsra055042; Mon, 23 Jan 2006 02:27:54 -0500 Message-ID: <43D4857A.5060407@gmail.com> Date: Mon, 23 Jan 2006 07:27:00 -0000 From: Bruce Korb User-Agent: Mozilla Thunderbird 1.0.7 (X11/20050923) MIME-Version: 1.0 To: Vale Group CC: insight@sourceware.org Subject: Re: Insight won't let me use the source any more References: <1132311131.437db25b30ca0@imp2-g19.free.fr> <437E575D.2000709@redhat.com> <43D421FC.9040003@gnu.org> <002101c61fc6$c9d67aa0$0100a8c0@abitceleron> In-Reply-To: <002101c61fc6$c9d67aa0$0100a8c0@abitceleron> Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00027.txt.bz2 Vale Group wrote: >Bruce Korb wrote: > > >>...I cannot get Insight to let me do source level debugging... >>What's the secret? >> >> > >The first question that pops to mind is, did you switch the compilation to your >program-under-study to MinGW from Cygwin, for instance? > No, but I did retype, "make" from the affected directory instead of the top and it was a "VPATH" build. I could see the sources again once I linked the sources into the build directory, so the glitch is more likely to do with some compile option or another. So, I do not know the cause, but my best guess at the moment is some funny compiler option. Thanks. Regards, Bruce