GNU bug report logs - #39140
28.0.50; gdb-mode incorrectly responds to C-d when a python interpreter is running

Previous Next

Package: emacs;

Reported by: Vladimir Nikishkin <lockywolf <at> gmail.com>

Date: Wed, 15 Jan 2020 01:26:02 UTC

Severity: normal

Found in version 28.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Vladimir Nikishkin <lockywolf <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 39140 <at> debbugs.gnu.org
Subject: bug#39140: 28.0.50; gdb-mode incorrectly responds to C-d when a python interpreter is running
Date: Tue, 21 Jan 2020 10:59:52 +0800
On my machine, Ctrl-D ends only the python interpreter in plain gdb,
but ends both python and gdb when gdb is launched with the MI
interpreter gdb -i=mi
That is, the general interpreter and the -i=mi interpreter seem to
interpret Ctrl-D differently.
I am using GNU gdb (GDB) 8.3.1.

вт, 21 янв. 2020 г. в 02:04, Eli Zaretskii <eliz <at> gnu.org>:
>
> > From: Vladimir Nikishkin <lockywolf <at> gmail.com>
> > Date: Mon, 20 Jan 2020 09:15:38 +0800
> > Cc: 39140 <at> debbugs.gnu.org
> >
> > No, which is quite weird.
>
> Really weird, because it worked for me.



-- 
Yours sincerely, Vladimir Nikishkin




This bug report was last modified 5 years and 116 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.