--- Comment #4 from pinskia at gcc dot gnu dot org 2008-08-21 23:03 ---
see http://sourceware.org/bugzilla/show_bug.cgi?id=6656 also.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37196
--- Comment #3 from pinskia at gcc dot gnu dot org 2008-08-21 23:02 ---
(In reply to comment #2)
> It works if -g is omitted on the assembling step. Still, the debug information
> from the asm should not conflict with the original debug information, should
> it?
And at that point, this
--- Comment #2 from pip88nl at gmail dot com 2008-08-21 22:56 ---
It works if -g is omitted on the assembling step. Still, the debug information
from the asm should not conflict with the original debug information, should
it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37196
--- Comment #1 from pinskia at gcc dot gnu dot org 2008-08-21 22:32 ---
The issue is here:
g++ -g -c test.s -o test.o
Don't use -g with assembly code that already has debugging info in it. Also I
think this was just fixed on the trunk of binutils lately where it checks to
make sure th
