This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20604] Using quit() causes a infinity loop which and can not exit gdb
- From: "tromey at sourceware dot org" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 14 Sep 2016 03:08:09 +0000
- Subject: [Bug gdb/20604] Using quit() causes a infinity loop which and can not exit gdb
- Auto-submitted: auto-generated
- References: <bug-20604-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20604
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2016-09-14
CC| |tromey at sourceware dot org
Ever confirmed|0 |1
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
This is a funny one. My first thought was that it couldn't be possible,
but sure enough... the bug is that quit_command just passes its argument
to quit_force, which does the evaluation after messing with the
terminal settings.
I have a patch that changes this area a bit, in particular it does
the expression evaluation in quit_command and no longer passes the
expression to kill_or_detach (which is undocumented behavior and also,
I think, incorrect).
I'll send it to gdb-patches when I find the time to regression test.
--
You are receiving this mail because:
You are on the CC list for the bug.