unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Volunteers to implement test for stuff called at startup?
Date: Mon, 02 May 2016 18:32:53 +0300	[thread overview]
Message-ID: <8360uwmq56.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY3G9SDCq+ASGU3JURcrzXmhe6M-2LfcpD3PJ_oyDee1VA@mail.gmail.com> (message from Kaushal Modi on Mon, 02 May 2016 15:08:18 +0000)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Mon, 02 May 2016 15:08:18 +0000
> Cc: emacs-devel@gnu.org
> 
> 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.



  parent reply	other threads:[~2016-05-02 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-01 15:41 Volunteers to implement test for stuff called at startup? Eli Zaretskii
2016-05-01 23:07 ` Richard Stallman
2016-05-02 15:08   ` Kaushal Modi
2016-05-02 15:15     ` Robert Pluim
2016-05-02 15:23       ` Kaushal Modi
2016-05-02 15:32     ` Eli Zaretskii [this message]
2016-05-02 15:44       ` Kaushal Modi
2016-05-02 15:56         ` Eli Zaretskii
2016-05-02 16:23           ` Kaushal Modi
2016-05-11  2:05 ` John Wiegley

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=8360uwmq56.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=rms@gnu.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).