GNU bug report logs - #22287
25.1.50; Sudden jumping point in buffer

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: "Stefan-W. Hahn" <stefan.hahn <at> s-hahn.de>
Cc: 22287 <at> debbugs.gnu.org, deng <at> randomsample.de
Subject: Re: bug#22287: 25.1.50; Sudden jumping point in buffer
Date: Mon, 04 Jan 2016 17:22:50 +0200

> Date: Sun, 3 Jan 2016 21:51:04 +0100
> From: "Stefan-W. Hahn" <stefan.hahn <at> s-hahn.de>
> Cc: 22287 <at> debbugs.gnu.org
> 
> | *** sem end2: buffer intervals.c 49510->49391
> | *** sem end2: timer nil
> | *** sem end2: idle-timer ([nil 0 1 0 t semantic-idle-scheduler-function nil 
> idle 0] [nil 0 60 0 t semantic-idle-scheduler-work-function nil idle 0])
> | *** sem end2: post-command-hook (diff-post-command-hook t)
> | *** sem end2: pre-command-hook nil
> `----
> 
> When switching semantic-mode off, the error seems not to be reproducible.
> 
> This should it be for today.

Thank you for your efforts.

It strikes me that a much more efficient way of finding who moves
point would be by setting a watchpoint on that buffer's value of
point, with commands like this:

 xbacktrace
 continue
 end

Then, whenever point changes in that buffer, you should see a Lisp
backtrace which will show the offending code.

Let me know if you need further help with setting up such a watchpoint
in GDB.

Previous Next

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