On Tue, Nov 18, 2014 at 11:14 AM, Michael Matz <m...@suse.de> wrote: > Hi, > > On Mon, 17 Nov 2014, Richard Biener wrote: > >> This means I can no longer interrupt a compile that is running too long? > > No, that's not what it means, cc1 will also get the SIGINT. > >> You should instead debug the actual compiler, not the driver. > > -wrapper is specifically also for invoking cc1 with gdb from the driver > (that's the usecase documented with -wrapper), so it better should work as > intended. I don't know what problems Patrick had with that, though. For > me gcc -wrapper gdb,--args works as expected (as in ^C interrupts cc1 > returning to gdb).
Yes it does for me too. But pressing ^C in gdb while cc1 is not running (by accident or with intention, e.g. pressing ^C to quickly clear the command prompt) will kill the driver and gdb after it. It's not a huge problem but it does cause some inconvenience for users of -wrapper gdb. > > > Ciao, > Michael.
