From: Noam Postavsky <npostavs@gmail.com>
To: Leah Neukirchen <leah@vuxu.org>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 35273@debbugs.gnu.org
Subject: bug#35273: "Marker does not point anywhere" when reading next article
Date: Tue, 16 Apr 2019 08:38:20 -0400 [thread overview]
Message-ID: <87zhoqxgzn.fsf@gmail.com> (raw)
In-Reply-To: <8736mkgu83.fsf@vuxu.org> (Leah Neukirchen's message of "Sun, 14 Apr 2019 23:19:56 +0200")
Leah Neukirchen <leah@vuxu.org> writes:
> If you have other ideas how I can debug it myself, please tell me.
If you can reproduce it reliably, setting (setq debug-on-signal t) just
before might help get a backtrace.
If that also doesn't work you could record the backtrace from a
signal-hook-function:
(defvar bug-35273-last-backtrace nil)
(defun bug-35273-record-backtrace (err data)
(when (and (eq err 'error)
(equal data '("Marker does not point anywhere")))
(setq bug-35273-last-backtrace
(backtrace-frames 'signal)))
(let ((signal-hook-function nil))
(signal err data)))
(setq signal-hook-function #'bug-35273-record-backtrace)
Or if you can run under gdb, just set a breakpoint in the C code where
that error is raised.
next prev parent reply other threads:[~2019-04-16 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 13:42 bug#35273: "Marker does not point anywhere" when reading next article Leah Neukirchen
2019-04-14 16:31 ` Basil L. Contovounesios
2019-04-14 21:19 ` Leah Neukirchen
2019-04-16 12:38 ` Noam Postavsky [this message]
2019-04-16 12:50 ` Leah Neukirchen
2019-04-16 13:13 ` Noam Postavsky
2019-04-16 13:21 ` Leah Neukirchen
2019-04-16 13:56 ` Noam Postavsky
2019-04-16 14:04 ` Leah Neukirchen
2019-04-16 15:02 ` Eli Zaretskii
2019-04-20 12:05 ` Noam Postavsky
2019-04-20 13:44 ` Eli Zaretskii
2019-04-20 16:20 ` Eli Zaretskii
2019-04-27 16:17 ` Noam Postavsky
2019-04-27 16:49 ` Eli Zaretskii
2019-04-27 19:28 ` Noam Postavsky
2019-04-27 19:35 ` Eli Zaretskii
2019-04-28 12:45 ` Noam Postavsky
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=87zhoqxgzn.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35273@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=leah@vuxu.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.
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.