[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43896: 28.0.50; End of file during parsing ~/.pop3-uidl
From: |
Lars Ingebrigtsen |
Subject: |
bug#43896: 28.0.50; End of file during parsing ~/.pop3-uidl |
Date: |
Sun, 11 Oct 2020 06:40:22 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
(Please keep the debbugs address in the Cc header.)
Mats Lidell <matsl@gnu.org> writes:
>> Lars Ingebrigtsen writes:
>> I'm not sure whether that file looks strange or not? It looks
>> well-formed, at least.
>
> Yes, you are right. Today I can't recreate that particular error.
>
>> But a backtrace would be helpful. (setq debug-on-error t), repeat the
>> bug and post the resulting backtrace.
>
> Today I get the following error in *Messages*
>
> Mail source (pop :server fencepost.gnu.org :port 995 :user matsl
> :authentication apop :stream ssl :leave 14) failed:
> (wrong-type-argument listp !!)
I'm not sure whether that looks related or not...
> My mail-sources looks like this which seems OK.
>
> (setq mail-sources
> '((pop :server "fencepost.gnu.org" :port 995 :user "matsl"
> :authentication apop :stream ssl :leave 14)))
>
> Setting debug on error or debug on quit does not produce any
> backtrace. Is it because this happens in a gnus-byte-compile section?
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. But it may give you many backtraces,
because it basically makes most ignored errors give you a backtrace, so
it should only be set just before you run this stuff and then switched
off again.