Problems with the debug information and C++

Ralf Corsepius ralf.corsepius at
Thu Jan 22 13:49:59 UTC 2009

Without having looked into details, some random comments interspersed:

Sebastian Huber wrote:
> Hi,

> Command line:
> powerpc-rtems4.10-gcc test.cpp -lstdc++ && objdump -W a.out > /dev/null

This compiler call is invalid.

You _must_ use *-g++ to link c++ code - It would be a random accident, 
should this example work.

> Output:
> Like in the previous mail.
>> There are many more warnings but they differ only in the numbers.  The
>> error and the overlap warning is new in 4.9 and CVS HEAD.  I noticed
>> this also on m68k.  Is this something that may cause harm?
> One of our customers reported that he cannot debug his application with his
> debugger.
What is "his debugger"?

> The support of the debugger vendor confirmed problem reports from
> various customers with GCC version 4.3.2.

Well, ... that's the usual excuse of debugger vendors utilize. I 
wouldn't give much about it ;)

I am not aware about any particular gcc-4.3.2 debug format specific 
change. Only the usual "imperfection" of SW.

> Does anyone know if this is more
> likely a RTEMS or GCC problem?
There is nothing special about powerpc-rtems-GCC. It's more or less a 
vanilla powerpc-elf GCC.

> I am unsure if I should write a GCC bug report.
I'd recommend to ask on the GCC list, ideally accompanied with a code 
example. It would not be the first time, somebody is facing an issue 
some specialist is very familiar with.


More information about the users mailing list