emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Eli Zaretskii
Subject: Re: Volunteers to implement test for stuff called at startup?
Date: Mon, 02 May 2016 18:32:53 +0300

> From: Kaushal Modi <address@hidden>
> Date: Mon, 02 May 2016 15:08:18 +0000
> Cc: address@hidden
> 
> Starting today morning (probably my first build after the update in 
> src/process.c), I am unable to update M-x
> list-packages. I keep on getting the below error.
> 
> =====
> 
> Importing package-keyring.gpg...done
> error in process filter: End of file during parsing
> 
> =====
> 
> The below is not helping me here as this error originates in C.
> 
> (setq debug-on-message "error in process filter")
> 
> I do not know for sure if the update in process.c or some package in GNU 
> elpa/melpa would cause this.

The changes in process.c are unlikely to be the culprit, as they
didn't change anything on your platform, just moved existing code
around.

But if you provide an exact recipe, I can try this on my machine and
see what I come up with.

> Can you please provide me pointers to help provide good debug info?

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.

> Also can that error be improved to give more info as to which file
> caused the "End of file during parsing" error?

What improvement did you have in mind?  The error message generally
means the stream from which the Emacs reader was reading hit EOF.

In any case, I suggest to postpone this latter issue until you find
out the cause of the problem, because otherwise we are discussing a
situation we don't sufficiently understand.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]