GNU bug report logs - #35273
"Marker does not point anywhere" when reading next article

Previous Next

Packages: emacs, gnus;

Reported by: Leah Neukirchen <leah <at> vuxu.org>

Date: Sun, 14 Apr 2019 15:59:01 UTC

Severity: normal

Tags: fixed, patch

Found in version 5.13

Fixed in version 26.3

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Noam Postavsky <npostavs <at> gmail.com>
To: Leah Neukirchen <leah <at> vuxu.org>
Cc: "Basil L. Contovounesios" <contovob <at> tcd.ie>, 35273 <at> debbugs.gnu.org
Subject: bug#35273: "Marker does not point anywhere" when reading next article
Date: Tue, 16 Apr 2019 08:38:20 -0400

Leah Neukirchen <leah <at> 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.
This bug report was last modified 6 years and 23 days ago.

Previous Next

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