Re: Volunteers to implement test for stuff called at startup?

[Eli Zaretskii <eliz@gnu.org>]

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Mon, 02 May 2016 15:44:24 +0000
> Cc: emacs-devel@gnu.org
> 
>  What improvement did you have in mind? The error message generally
>  means the stream from which the Emacs reader was reading hit EOF.
> 
> As someone reported in a Melpa github issue, the problem is that the Melpa archive-contents (
> http://melpa.org/packages/archive-contents ) is corrupted (as of writing this).
> 
> If the above problem is fixed at the time of viewing this email, this is what archive-contents ended with: 
> 
> =====
> https://github.com/cosmicexplorer/cloc-emacs") (:keywords "cloc" "count" "source" "code" "lines"))]) (clmemo
> . [(20160326 923) nil "Change Log MEMO" tar ((:url . "https://github.com/ataka/clmemo") (:keywords
> "convenience"))]) (cljsbuild-mode . [(20160402 1000) nil "A minor mode for the ClojureScript 'lein cljsbuild'
> command" single ((:url . "http://github.com/kototama/cljsbuild-mode") (:keywords "clojure" "clojurescript"
> "leiningen" "compilation"))]) (cljr-helm . [(20150425 1307) ((clj-refactor (0 13 0)) (helm (1 5 6))) "Wraps clojure
> refactor commands with helm" single ((:url . "https://github.com/philjackson/cljr-he
> =====
> 
> 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.

As you see from the detailed backtrace I posted for your bug report,
the problem happens when Emacs tries to read from an empty string, so
there's no file to report.