From: Mats Lidell <matsl@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Mats Lidell <matsl@gnu.org>, 43896@debbugs.gnu.org
Subject: bug#43896: 28.0.50; End of file during parsing ~/.pop3-uidl
Date: Sun, 11 Oct 2020 22:18:31 +0200 [thread overview]
Message-ID: <87o8l87bzc.fsf@gnu.org> (raw)
In-Reply-To: <87o8l9gytl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 11 Oct 2020 06:40:22 +0200")
> Lars Ingebrigtsen writes:
> (Please keep the debbugs address in the Cc header.)
OOPS! Sorry. Trying to learn using debbugs.
[...]
> Is gnus-byte-compile involved here? I'm not sure I follow.
>
> Anyway, I forgot about all the error-catching stuff here.
>
> (setq debug-on-signal t)
>
> should give you a backtrace.
I was just guessing about gnus-byte-compile causing problems. Reading the help
for debug-on-error I now think it is that the code is executed in a
condition-case that stops the backtrace from being created. Using
debug-on-signal does not seem to help in this respect either. (But I don't
know elisp good enough to tell.) Anyway the patch provided by Andreas seems to
do the trick.
next prev parent reply other threads:[~2020-10-11 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 22:34 bug#43896: 28.0.50; End of file during parsing ~/.pop3-uidl Mats Lidell
2020-10-10 20:38 ` Lars Ingebrigtsen
[not found] ` <87ft6lr82f.fsf@gnu.org>
2020-10-11 4:40 ` Lars Ingebrigtsen
2020-10-11 20:18 ` Mats Lidell [this message]
2020-10-11 12:06 ` Andreas Schwab
2020-10-11 20:11 ` Mats Lidell
2021-01-06 20:29 ` bug#43896: (no subject) Mats Lidell
2021-01-07 12:21 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8l87bzc.fsf@gnu.org \
--to=matsl@gnu.org \
--cc=43896@debbugs.gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).