delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mailnull set sender to djgpp-workers-bounces using -f |
Date: | Mon, 4 Feb 2002 14:30:58 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | pavenis AT lanet DOT lv |
cc: | djgpp-workers AT delorie DOT com |
Subject: | Re: gcc-3.X and GDB |
In-Reply-To: | <3C5E827C.11149.8DDF2@localhost> |
Message-ID: | <Pine.SUN.3.91.1020204142928.10902D-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Mon, 4 Feb 2002 pavenis AT lanet DOT lv wrote: > Reproduced it under Linux: > - stripped debug information fromn one my static object library > - linked one executable (more that one C++ source file) with > this library > - command 'where' showed wrong locations in main.cc for > procedures in stripped library > > It doesn't seem to happen with shared libraries though, but they are usualy > built with debug info. > > Perhaps I should prepare some nice test example to be sent to GDB > mailing list. Yes, that would probably allow the maintainers to identify the bug much faster. > Anyway I think it could also be some problem in linker at time of merging > debug info from fultiple source files. If so, perhaps "objdump --debugging" will show enough information to find the reason for GDB's misbehavior.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |