Launchpad has imported 8 comments from the remote bug at http://sourceware.org/bugzilla/show_bug.cgi?id=6656.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-06-18T19:40:46+00:00 Matthias Klose wrote: seen with current trunk, not with the 2.18 branch, testcase taken from the darcs configury. echo -e '#include "test2.h"\nint main (int argc, char** argv) {callme(); return 1;}' > test2.c echo 'int callme() {}' > test2.h gcc -S -g test2.c -o test2.s; gcc test2.s -o test2 -g test2.s: Assembler messages: test2.s:31: Error: file number 2 already allocated omitting the -g for the linking avoids the error. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/1 ------------------------------------------------------------------------ On 2008-06-18T20:11:14+00:00 Alan Modra wrote: target? gcc version? Really, for assembler errors, you ought to give us the assembler input, removing the dependency on gcc. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/2 ------------------------------------------------------------------------ On 2008-06-18T20:31:04+00:00 Matthias Klose wrote: Created attachment 2783 testcase (.s file generated by GCC-4.3.1) this is on i386-linux-gnu, built with GCC-4.3.1 release. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/3 ------------------------------------------------------------------------ On 2008-06-18T20:35:47+00:00 Matthias Klose wrote: Created attachment 2784 testcase (.s file for ia64, generated by GCC-4.3.1) on ia64-linux-gnu the testcase fails with both 2.18 branch and the trunk. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/4 ------------------------------------------------------------------------ On 2008-06-22T03:49:02+00:00 Alan Modra wrote: Actually, I should have recognized the problem just from the description. Asking the assembler to generate dwarf debug info, when the file already has debug info generated by the compiler, is just one of those things you should not do. Of course, the assembler ought to give a better error message.. You see, the compiler emits file and line number info referring to the C (or other language) source file and line numbers, while "as -g" emits file and line number info for the assembly file. Having both sets of debug info doesn't make much sense, since they give contradictory information. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/5 ------------------------------------------------------------------------ On 2008-07-12T18:46:11+00:00 Hjl-tools wrote: Alan is correct. You shouldn't use "gcc -g" on assembly code which already has debug info. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/7 ------------------------------------------------------------------------ On 2008-08-05T08:14:50+00:00 Alan Modra wrote: Fixing. Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/9 ------------------------------------------------------------------------ On 2008-08-05T08:16:11+00:00 Alan Modra wrote: http://sourceware.org/ml/binutils-cvs/2008-08/msg00027.html Reply at: https://bugs.launchpad.net/binutils/+bug/240884/comments/10 ** Changed in: binutils Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/240884 Title: -g and compiling via assembly fails -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
