From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31467 invoked by alias); 4 Sep 2003 20:11:34 -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 31445 invoked from network); 4 Sep 2003 20:11:33 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 4 Sep 2003 20:11:33 -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 h84KBWl27082 for ; Thu, 4 Sep 2003 16:11:32 -0400 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 h84KBVs12115; Thu, 4 Sep 2003 16:11:31 -0400 Received: from [150.1.200.14] (vpn50-16.rdu.redhat.com [172.16.50.16]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id h84KBUA3026421; Thu, 4 Sep 2003 16:11:30 -0400 Subject: Re: Problem with source paths with new Cygwin release From: Keith Seitz To: Kristian Otnes Cc: "insight@sources.redhat.com" In-Reply-To: <3F5795CF@webmail.aktivepost.no> References: <3F5795CF@webmail.aktivepost.no> Content-Type: text/plain Organization: Message-Id: <1062706426.1585.5.camel@lindt.uglyboxes.com> Mime-Version: 1.0 Date: Thu, 04 Sep 2003 20:11:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-q3/txt/msg00147.txt.bz2 On Thu, 2003-09-04 at 12:57, Kristian Otnes wrote: > Today after updating the Cygwin environment, Insight started > having problems with source paths when doing high level debugging. > Most source files are shown only in assembly code, and when > using the Insight function browser, the source paths seem to have > been stripped away from almost all source files. Thus, only > assembly code is shown. Does command line gdb (of the same version) suffer from the same problem? > Anyone happen to know the reason? Not off hand, sorry. > Is it likely that rebuilding Insight after an upgrade would also > solve the problem? Not sure. There's a relatively easy way to find out, though! ;-) Keiht