Re: source code location at build time affects ups

In message <[email protected]>
          Callum Gibson <[email protected]> wrote:

> with "g++ -gstabs+ -o tctc test.cc"
> and get no source with "ups tctc", but ok with "ddd tctc".
> 
> With -gdwarf-2, it works (with no crash) in ups. Moving the source to
> a subdirectory and recompiling still works, even if run from a different
> subdirectory (I'm guessing the path to the source is specified as relative
> to the binary in this case). Specifying a full path to the source file
> causes ups to exit with the following:

The rune time startup code that gcc has used probably has DWARF debug
data in it. If that is the case then you must also use DWARF as ups will
only use one or the other and it checks for DWARF first I think so if it
finds any DWARF debug data at all then all the stabs are ignored.

That decision applies on a per shared library basis so it doesn't matter
if libc.so contains DWARF but it does if crt1.o which is statically linked
to your program does.

> -g and -ggdb gives same results as dwarf-2.
> -gdwarf gives same results as stabs+
> All other forms of -g are unsupported on my compiler.

I think -gdwarf is DWARF 1 which ups doesn't support.

Tom

-- 
Tom Hughes ([email protected])
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/