GNU bug report logs - #11265
24.0.94; gdb-mi very slow on Windows

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: karl-heinz <at> schneider-inet.de
Subject: bug#11265: closed (Re: bug#11265: 24.0.94; gdb-mi very slow on
 Windows)
Date: Tue, 05 Nov 2019 13:48:04 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#11265: 24.0.94; gdb-mi very slow on Windows

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 11265 <at> debbugs.gnu.org.

-- 
11265: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11265
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Stefan Kangas <stefan <at> marxist.se>
To: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>,
 11265-done <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Tue, 5 Nov 2019 14:46:55 +0100

Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de> writes:

> >This was 7 years ago.  Are you still seeing this on a modern version of
> >Emacs?
>
> I think you can close this issue. I even don't use Emacs anymore for C++ coding these days. I even forgot about it, sorry.

Thanks for reporting back; closing the bug now.  If anyone else is
seeing this, please reopen the bug.

Best regards,
Stefan Kangas

[Message part 3 (message/rfc822, inline)]

From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
To: <bug-gnu-emacs <at> gnu.org>
Subject: 24.0.94; gdb-mi very slow on Windows
Date: Tue, 17 Apr 2012 16:21:05 +0200

I use Emacs for C/C++ development on Windows XP. Since update to Emacs
24.0.94 I discovered that debugging with gdb-mi is very slow.

Right after starting debugging performance is ok, but after a while
using the debugger (adding breakpoints, removing breakpoints setting
conditions, etc...) becomes very very slow.

After a while Emacs is consuming 100% of CPU power for a while just
for typing a single character into the gdb-buffer (not sending it to 
GDB).
GDB commands like "next" or "step" take then several seconds until
all buffers are refreshed.

Previous Next

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