The most efficient method is to debug this in C. By limiting yourself
to Lisp, you are unnecessarily making your job much harder and wasting
your time on something that is very easy to do using GDB. Time to
cross that bridge, perhaps? Here are the instructions in case you
decide to do it:
Just set a breakpoint in Fsignal, and when it breaks, type "bt" to
display the backtrace. Start GDB from the src directory, so it will
display both C and Lisp backtrace when you type that command.
Additional info is in etc/DEBUG.
Thanks! Looks like I will need to cross that bridge eventually. For this problem though, the source is identified, but I wished that error gave a direct pointer (see below).
What improvement did you have in mind? The error message generally
means the stream from which the Emacs reader was reading hit EOF.
If the above problem is fixed at the time of viewing this email, this is what archive-contents ended with:
=====
=====
So the improvement request is if it's possible for emacs to print the path to the offending file so that, in this case, the error would directly tell that EOF error was found in archive-contents downloaded from Melpa.