Re: stabs difference gcc 2.95.3 -> 3.4.3

[Fabian Cenedese <Cenedese@indel.ch>]

>> This is the working file of gcc 2.95.3, looking up _TASK_CLASS_NAME_::Action:
>> GNU gdb 6.2.50_2004-10-14-cvs
>
>First of all, this is an older GDB.  You might want to try a current
>one.

That was just lying around from my last experiments. As it worked fine
with output of the older gcc I had no reason (yet) to upgrade.

>Secondly, since you're trying to debug C++ with stabs, the basic
>reaction is that you'll get what you deserve - the stabs produced
>by GCC are missing a lot of information that's available in the default
>DWARF-2 format.

Well, as the currently used compiler 2.95.3 is even older and I supposed
that the stabs format should be compatible I didn't especially try the
newest versions but I may now.

>> First thing: why does gdb say that the function is in a file compiled without
>> debugging when it still knows where to find it?
>
>We'd need a testcase, sorry.  But this is likely to be related to...
>
>> Second thing: why is the assembler file given as source file? Of course it
>> _is_ the source file given our two steps compiling. But the same was true
>> with the old tool chain where it worked fine. Also, in the generated assembler
>> file is the first line a directive:
>>       .file   "CTaskTemplateClass.cpp"
>> so it should be clear where this code comes from.
>
>... this.

I thought so. When I do it in one step it works better, still not perfect though.

>Probably gas has been passed the -g option, and generated
>its own debug information, which caused GDB to see debug info for the
>assembly file instead of for the source file.  You might want to check
>that.

The -g is given to gcc, I don't know if that gets passed on to as. But so 
was the setup with the older compiler as well, where it worked.

>> Just for checking if this would work better I also tried -gdwarf-2. Got even worse:
>> GNU gdb 6.2.50_2004-10-14-cvs
>> This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-eabi"...Dwarf Error: Could not find abbrev number 128
>>  [in module /cygdrive/n/IMD/Bin/Gnu32_new/gcc3.x]
>
>Either this is a linker bug, or a GDB bug.  In either case, it is
>almost certainly fixed in current versions of either.  The current
>releases are GCC 4.1.0, binutils 2.16.1, and GDB 6.4.

Hehe... I almost expected this answer, that's the same we tell our
customers when they don't have our newest tools. I'll see what
I can do.

Thanks for answering.

bye  Fabi