From: pmlists@free.fr (Peter Münster)
To: ding@gnus.org
Subject: Re: mouse pointer moves unexpectedly
Date: Sat, 22 Jan 2011 22:01:37 +0100 [thread overview]
Message-ID: <87bp38tzym.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: <87zkqsu635.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> The people who can reproduce the bug has to debug it. :-)
I would like to do that. My idea is to start from a backtrace, then
analysing the functions that are called when pressing "n".
But I need some help: how can I get such a backtrace? debug-on-error
does not work, since there is no error (just mouse-movement...).
TIA for any help,
--
Peter Münster
Contact information: http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2011-01-22 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 7:30 Peter Münster
2011-01-22 4:51 ` Lars Ingebrigtsen
2011-01-22 8:24 ` Peter Münster
2011-01-22 18:10 ` Lars Ingebrigtsen
2011-01-22 18:42 ` Peter Münster
2011-01-22 18:49 ` Lars Ingebrigtsen
2011-01-22 21:01 ` Peter Münster [this message]
2011-01-22 21:11 ` Lars Ingebrigtsen
2011-01-22 21:40 ` Peter Münster
2011-01-22 21:14 ` Lars Ingebrigtsen
2011-01-22 21:15 ` Lars Ingebrigtsen
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=87bp38tzym.fsf@micropit.couberia.bzh \
--to=pmlists@free.fr \
--cc=ding@gnus.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).