source code location at build time affects ups
"William F. Dowling" <[email protected]> Tue, 30 Nov 2004 15:26:27 -0500
| Newsgroups | gmane.comp.debugging.ups.user |
|---|---|
| Message-ID | <1101846387.4748.62.camel@wdowlingpc> |
I have noticed something odd under Linux (but not Solaris), debugging code built with g++ 3.2.3. For ups to work, the source code must be in the working directory when the executable is built. The first example below fails; the second suceeds. $ g++ -g -o hello /home/wdowling/src/hello.cpp # non-trivial path to source $ /links/extern/i686/bin/ups hello DWARF error : dwarf_attr - no entry (DIE /home/wdowling/src/hello.cpp <2643><11>) Already saved typename rebind<char> in this CU <2632> ups starts up, but no source code is visible; if a source path is added (on the command line or in the interface) the source is visible, but breakpoints cannot be set nor data examined. $ cp ~/src/hello.cpp . $ g++ -g -o hello ./hello.cpp # source in working directory $ /links/extern/i686/bin/ups hello Already saved typename rebind<char> in this CU <2632> ups starts, source coide is available, breakpoints can be set and data examined. Has anyone else seen this? Thanks, Will -- William F. Dowling Thomson/ISI (www.isinet.com) 215-386-0100 x-1156 ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________