From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26995 invoked by alias); 24 Sep 2003 19:03:13 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26935 invoked from network); 24 Sep 2003 19:03:11 -0000 Received: from unknown (HELO mail44.fg.online.no) (148.122.161.44) by sources.redhat.com with SMTP; 24 Sep 2003 19:03:11 -0000 Received: from zinfandel (ti221110a080-3452.bb.online.no [80.213.13.124]) by mail44.fg.online.no (8.9.3p2/8.9.3) with ESMTP id VAA18918; Wed, 24 Sep 2003 21:03:10 +0200 (MEST) From: "Kristian Otnes" To: Cc: Subject: RE: GDB/ELF/Cygwin source path problem Date: Wed, 24 Sep 2003 19:03:00 -0000 Organization: Tevero Message-ID: <001301c382ce$80377da0$770a2f0a@zinfandel> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <200309241211.h8OCB8IG010503@duracef.shout.net> Importance: Normal X-SW-Source: 2003-09/txt/msg00303.txt.bz2 Michael, thanks for your time and help. I haven't specifically looked at the assembly files, but I have looked at the resulting ELF file which includes the debug info. It is the ELF file that is used by the GDB symbol reader. And the paths are in there. The thing was that the same ELF file gave different results with Cygwin version 1.3.22-1 compared to the current 1.5.x-y versions available. We are using an old GCC cross compiler, so it may be that the resulting ELF format has changed in newer GCC versions, but I am not so sure about that. But for various reasons we don't want to change the compiler now. Anyway, I just checked on Cygwin, and there has been some changes in the stat() and dirent() internal structures when going from 1.3.x to 1.5.x, not fstat() as I indicated. GDB seems to be using them, but that may be a sidetrack here. Anyway, what I wanted was to do some old fashioned debugging with rebuilding Insight (and GDB) with some printf's inside to see what was going on inside the symbol reader. And if anyone knows whereabouts source file names and their paths are read, I would appreciate a tip. Kris -----Original Message----- From: Michael Elizabeth Chastain [mailto:mec@shout.net] Sent: 24. september 2003 14:11 To: gdb@sources.redhat.com; kristian.otnes@tevero.no Subject: Re: GDB/ELF/Cygwin source path problem Try "gcc -S ...", with all the options that you normally use, and adding a "-S". Then look in the generated assembly code and see what the file names look like. That might help. Try doing the exact "gcc -S ..." with the old working cygwin dll and the new non-working cygwin dll. Perhaps cygwin.dll changed in such a way that gcc emits new information now. Try running the exact same executable with the old and new cygwin dll. That is, not re-compiling, and with the *exact* same file. These things would help localize the problem. Apologies if this is too simple and you have already done it. Michael C GDB QA Guy