https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89858
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> --- Not very helpful - you need follow the fork to the actual compiler binary. The easiest way to do this is to run the compiler with -v appended and the cut&paste the line where it executes the cc1plus binary and run that inside the debugger. It should look somewhat like /usr/lib64/gcc/x86_64-suse-linux/4.8/cc1plus -quiet -v -D_GNU_SOURCE t.c -quiet -dumpbase t.c -mtune=generic -march=x86-64 -auxbase t -version -o /tmp/ccbh6DsK.s and you then do > gdb --args usr/lib64/gcc/x86_64-suse-linux/4.8/cc1plus -quiet -v > -D_GNU_SOURCE t.c -quiet -dumpbase t.c -mtune=generic -march=x86-64 -auxbase > t -version -o /tmp/ccbh6DsK.s ... (gdb) run ... Illegal Instruction (gdb) disassemble cut&paste the context around the PC marker ==>
