Re: source code location at build time affects ups

On 01 Dec 15:12, William F. Dowling wrote:
}With -gstabs+ and -gstabs I don't get any error message, but still the
}source is not visible.  It's almost as though dwarf is being used OK,
}but dwarf is not handling the path to the source correctly.

I've sort of been half-following this thread, but as a further data point
in case it hasn't been mentioned, here is my experience. For Linux, we've
always had to specify -gstabs to get C programs to work properly with ups.
Secondly, C++ compiled with the same flags has blank source, as for William,
but works fine with ddd (and presumably gdb). Identical results with stabs+.
Adding the source path in ups doesn't have any effect.

Having a brief look with nm and strings through the compiled binary and
comparing a C (which works) and C++ (which doesn't) program doesn't highlight
anything obvious to my untrained eye. I can see references to main and the
source file (full path) which contains it in both cases.

-- 
Callum Gibson          [email protected]          61 438 266 463 (M)
Rates & ICT IT, Deutsche Bank, Australia [/]  61 2 9258 1620 (W)
### The opinions in this message are mine and not Deutsche's ###