https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71918
--- Comment #5 from Markus Trippelsdorf <trippels at gcc dot gnu.org> --- (In reply to Andrew Pinski from comment #3) > (In reply to jordyruiz from comment #2) > > Hi, > > > > I have managed to output a cvc4_operand_visitor.ii file, but it's 77182 > > lines long, I'm afraid this may not be what you're looking for. > > > > I use an Intel Core 2 Duo CPU E6850 @ 3.00GHz. > > > > I ran gcc under gdb but I don't see any information about which illegal > > instruction was hit, sorry. Could you tell me how I could extract that info? > > > > Most likely you need to follow fork in gdb and then disassemble $pc,$pc+0x10 > . Yes. set follow-fork-mode child run disass (and please also post the backtrace) bt
