From: Eli Zaretskii <eliz@gnu.org>
To: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
Cc: deng@randomsample.de, 22287@debbugs.gnu.org
Subject: bug#22287: 25.1.50; Sudden jumping point in buffer
Date: Tue, 05 Jan 2016 18:27:22 +0200 [thread overview]
Message-ID: <838u4456vp.fsf@gnu.org> (raw)
In-Reply-To: <20160105150121.GA10231@scotty.home> (stefan.hahn@s-hahn.de)
> Date: Tue, 5 Jan 2016 16:01:22 +0100
> From: "Stefan-W. Hahn" <stefan.hahn@s-hahn.de>
> Cc: deng@randomsample.de, 22287@debbugs.gnu.org
>
> Thanks for this hint. I wasn't aware of this, after reading the good
> documentation etc/DEBUG, great possibilities.
>
> I've sat it up and am able to define a watchpoint which calls xbacktrace. I
> have to play around with it a little, because in this straight forward
> atempt, it is to slow. There is no possibility to do any real keystrokes in
> the debuged emacs.
Probably because you defined the watchpoint so that GDB was forced to
use software watchpoints, rather than hardware-assisted watchpoints.
The latter doesn't slow down Emacs.
If you tell how you defined the watchpoint, I might be able to help
you redefine it so that hardware-assisted watchpoints are used by GDB.
next prev parent reply other threads:[~2016-01-05 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 11:10 bug#22287: 25.1.50; Sudden jumping point in buffer Stefan-W. Hahn
2016-01-03 11:26 ` David Engster
2016-01-03 13:07 ` Stefan-W. Hahn
2016-01-03 15:47 ` David Engster
2016-01-03 20:51 ` Stefan-W. Hahn
2016-01-04 15:22 ` Eli Zaretskii
2016-01-05 15:01 ` Stefan-W. Hahn
2016-01-05 16:27 ` Eli Zaretskii [this message]
2016-01-05 19:51 ` Stefan-W. Hahn
2016-01-05 20:12 ` Eli Zaretskii
2016-01-05 21:08 ` Stefan-W. Hahn
2016-01-06 14:13 ` Stefan-W. Hahn
2016-01-06 21:52 ` David Engster
2016-02-21 16:29 ` David Engster
2016-01-04 15:22 ` 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=838u4456vp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22287@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=stefan.hahn@s-hahn.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.