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

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 11265 in the body.
You can then email your comments to 11265 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

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.

Message #8 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: karl-heinz <at> schneider-inet.de
Cc: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Tue, 17 Apr 2012 20:10:56 +0300

> Date: Tue, 17 Apr 2012 16:21:05 +0200
> From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
> 
> 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.

Which version did you upgrade from?  IOW, with which version are you
comparing the speed?

> 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.

When this slowdown happens, is the GDB interaction buffer displayed?
If so, does it help to delete the window where the interaction buffer
is shown, so that the buffer is not displayed in any window?

(I'm trying to establish whether the slowness is related to display or
to something else.)

Another thing to try is start GDB like this:

  M-x gud-gdb RET

and see if the resulting session is as fast as what you were used to
before 24.0.94.

Message #11 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> gnu.org>
To: karl-heinz <at> schneider-inet.de
Cc: Eli Zaretskii <eliz <at> gnu.org>, 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Wed, 18 Apr 2012 09:56:37 +0800

> When this slowdown happens, is the GDB interaction buffer displayed?
> If so, does it help to delete the window where the interaction buffer
> is shown, so that the buffer is not displayed in any window?
>
> Another thing to try is start GDB like this:
>
>   M-x gud-gdb RET
>
> and see if the resulting session is as fast as what you were used to
> before 24.0.94.

In addition to what Eli suggested, try setting bidi-paragraph-direction
to 'left in the *gud* buffer and see if it makes a difference in speed.

Message #14 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: karl-heinz <at> schneider-inet.de
Cc: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Wed, 18 Apr 2012 19:30:39 +0300

[Please keep the bug address on the CC list, so that this whole
discussion gets archived.]

> Date: Wed, 18 Apr 2012 08:53:16 +0200
> From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
> 
> I discovered that the slowdown happens after restarting the process to 
> debug.
> I did the following procedure:
> 
> 1. Start the debugger (with process cmd-line).
> 2. Enter run to start the process
> 3. Debug the process
> 4. Enter kill to stop the process
> 5. Change code and recompile
> 6. Start again with step 2
> 
> Doing this three or four times debugging starts to get slow.

If you omit step 5, does the problem still happen?

> All debugging is done within the gud buffer using GDB commands.

If, instead of stopping the process in step 4, you kill the gud buffer
through which you interact with GDB, do you still see the slowdown
after several times that you kill and restart the debugging?

Message #17 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Wed, 18 Apr 2012 19:31:40 +0300

Forwarding this, for the record.

> Date: Wed, 18 Apr 2012 08:11:13 +0200
> From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
> 
> Previously I used Emacs 23.3. This version didn't use GDB/MI as far as 
> I
> know. This worked very well most of the time.
> 
>  From the slowdown Emacs isn't affected completely. It's just working 
> with the
> debugger buffer. Change the focus from any other buffer to the GUD 
> buffer or
> typing in the GUD buffer is very slow. The slow down happens while 
> working with
> GUD. I prefer the keyboard, so I enter the GDB commands into the GUD 
> buffer.
> Any other not GUD related buffer works with usual speed.
> 
> I tried gud-gdb as well. Speed is good but it has other drawbacks. It 
> doesn't
> display the breakpoints within the source buffer and the gdb completion 
> doesn't
> work.
> 
> Kalle
> 

Message #20 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Chong Yidong <cyd <at> gnu.org>
Cc: karl-heinz <at> schneider-inet.de, 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Wed, 18 Apr 2012 20:00:40 +0300

> From: Chong Yidong <cyd <at> gnu.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  11265 <at> debbugs.gnu.org
> Date: Wed, 18 Apr 2012 09:56:37 +0800
> 
> In addition to what Eli suggested, try setting bidi-paragraph-direction
> to 'left in the *gud* buffer and see if it makes a difference in speed.

I doubt that this could be related, since each time you type
"continue" in the gud buffer, there's an empty line after the
"Continuing" response.

Anyway, I did a long debugging session, got to about 1000 lines in the
gud buffer, but didn't see any perceptible slowdown.  So the reason is
still unclear.

Message #23 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Thu, 19 Apr 2012 08:10:09 +0200

>> I discovered that the slowdown happens after restarting the process 
>> to
>> debug.
>> I did the following procedure:
>>
>> 1. Start the debugger (with process cmd-line).
>> 2. Enter run to start the process
>> 3. Debug the process
>> 4. Enter kill to stop the process
>> 5. Change code and recompile
>> 6. Start again with step 2
>>
>> Doing this three or four times debugging starts to get slow.
>
> If you omit step 5, does the problem still happen?

Yes, the problem doesn't depend on recompiling. Its more to wait some
seconds before begin a new debugging cycle.

>
>> All debugging is done within the gud buffer using GDB commands.
>
> If, instead of stopping the process in step 4, you kill the gud 
> buffer
> through which you interact with GDB, do you still see the slowdown
> after several times that you kill and restart the debugging?

Killing the GUD buffer and starting a new debugging session totally
recovers to original performance.

Kalle

Message #26 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: karl-heinz <at> schneider-inet.de
Cc: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Fri, 20 Apr 2012 10:49:19 +0300

> Date: Thu, 19 Apr 2012 08:10:09 +0200
> From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
> Cc: <11265 <at> debbugs.gnu.org>
> 
> >> I discovered that the slowdown happens after restarting the process 
> >> to
> >> debug.
> >> I did the following procedure:
> >>
> >> 1. Start the debugger (with process cmd-line).
> >> 2. Enter run to start the process
> >> 3. Debug the process
> >> 4. Enter kill to stop the process
> >> 5. Change code and recompile
> >> 6. Start again with step 2
> >>
> >> Doing this three or four times debugging starts to get slow.
> >
> > If you omit step 5, does the problem still happen?
> 
> Yes, the problem doesn't depend on recompiling. Its more to wait some
> seconds before begin a new debugging cycle.
> 
> >
> >> All debugging is done within the gud buffer using GDB commands.
> >
> > If, instead of stopping the process in step 4, you kill the gud 
> > buffer
> > through which you interact with GDB, do you still see the slowdown
> > after several times that you kill and restart the debugging?
> 
> Killing the GUD buffer and starting a new debugging session totally
> recovers to original performance.

If you can try the current development code on the emacs-24 branch,
please see if the problem is still there.  Some related problems were
fixed recently, and maybe they also fix your problem.  If you cannot
try the current code, please revisit this after the next pretest
version is released, and report back.  Thanks.

Message #29 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Tue, 24 Apr 2012 16:57:22 +0200

> If you can try the current development code on the emacs-24 branch,
> please see if the problem is still there.  Some related problems were
> fixed recently, and maybe they also fix your problem.  If you cannot
> try the current code, please revisit this after the next pretest
> version is released, and report back.  Thanks.

I just downloaded the zip-package 24.1.50 of emacs. The problem is
still there.

Kalle

Message #32 received at 11265 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefan <at> marxist.se>
To: Karl-Heinz Schneider <karl-heinz <at> schneider-inet.de>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 11265 <at> debbugs.gnu.org
Subject: Re: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Fri, 01 Nov 2019 20:51:50 +0100

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

>> If you can try the current development code on the emacs-24 branch,
>> please see if the problem is still there.  Some related problems were
>> fixed recently, and maybe they also fix your problem.  If you cannot
>> try the current code, please revisit this after the next pretest
>> version is released, and report back.  Thanks.
>
> I just downloaded the zip-package 24.1.50 of emacs. The problem is
> still there.

This was 7 years ago.  Are you still seeing this on a modern version of
Emacs?

Best regards,
Stefan Kangas

Message #37 received at 11265-done <at> debbugs.gnu.org (full text, mbox):

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

Previous Next

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