From: Eli Zaretskii <eliz@gnu.org>
To: karl-heinz@schneider-inet.de
Cc: 11265@debbugs.gnu.org
Subject: bug#11265: 24.0.94; gdb-mi very slow on Windows
Date: Wed, 18 Apr 2012 19:30:39 +0300 [thread overview]
Message-ID: <83r4vl6lzk.fsf@gnu.org> (raw)
In-Reply-To: <4a9b5bb0b0553d31ee6df5994fd8a56d@schneider-inet.de>
[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@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?
next prev parent reply other threads:[~2012-04-18 16:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 14:21 bug#11265: 24.0.94; gdb-mi very slow on Windows Karl-Heinz Schneider
2012-04-17 17:10 ` Eli Zaretskii
2012-04-18 1:56 ` Chong Yidong
2012-04-18 17:00 ` Eli Zaretskii
[not found] ` <4a9b5bb0b0553d31ee6df5994fd8a56d@schneider-inet.de>
2012-04-18 16:30 ` Eli Zaretskii [this message]
2012-04-19 6:10 ` Karl-Heinz Schneider
2012-04-20 7:49 ` Eli Zaretskii
2012-04-24 14:57 ` Karl-Heinz Schneider
2019-11-01 19:51 ` Stefan Kangas
[not found] ` <21C01CB2-EBC0-47D7-8F57-D5801A15C5FD@schneider-inet.de>
2019-11-05 13:46 ` Stefan Kangas
[not found] ` <669ef4eefd097d3da673c9f368045ea2@schneider-inet.de>
2012-04-18 16:31 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r4vl6lzk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11265@debbugs.gnu.org \
--cc=karl-heinz@schneider-inet.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.