From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Kaushal Modi Newsgroups: gmane.emacs.devel Subject: Re: Volunteers to implement test for stuff called at startup? Date: Mon, 02 May 2016 15:44:24 +0000 Message-ID: References: <83y47tn5tv.fsf@gnu.org> <8360uwmq56.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c30c2c8c15b90531ddde51 X-Trace: ger.gmane.org 1462204115 5690 80.91.229.3 (2 May 2016 15:48:35 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 May 2016 15:48:35 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 02 17:48:34 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1axG5I-0002jg-4T for ged-emacs-devel@m.gmane.org; Mon, 02 May 2016 17:48:32 +0200 Original-Received: from localhost ([::1]:37352 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axG5E-0002dR-9i for ged-emacs-devel@m.gmane.org; Mon, 02 May 2016 11:48:28 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axG2C-0005RA-BM for emacs-devel@gnu.org; Mon, 02 May 2016 11:45:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1axG1z-0003tz-U6 for emacs-devel@gnu.org; Mon, 02 May 2016 11:45:14 -0400 Original-Received: from mail-ob0-x233.google.com ([2607:f8b0:4003:c01::233]:36302) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1axG1y-0003iC-La; Mon, 02 May 2016 11:45:07 -0400 Original-Received: by mail-ob0-x233.google.com with SMTP id j9so89851792obd.3; Mon, 02 May 2016 08:44:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=yeoLWBw469H+4eQjfUfs+6P+6/dj2TDSiv3eFST8Fc0=; b=DQB/hdPdjZ/eE34Gto+yHJlHEPAs0fzqsV2QFUKofjLQuJYcLiGtOuB479fRdWO4yR /GMEl1t50oGJIFlWeHXlOfS/+bYbnoR/8urS17kIK8lE5fRrw35imdCyl5LX345+BnUe a553Ly/6RKSMGgtkAS0w2sVmIsxAUq1UGiPPm4Twsv6+xfh9x7qK6rawYIWl1FMvkYgw /n2qeuLcyOB4C2fqm08fr0CKG7b9GAO/9UbOZ639DcxlOWpCzlI8xbgimFZkZD58HLYZ oN8w1isP+hj0MXAdtviwxzE9SQ2kYGtzk89vL9SBKtjYNgMPrYUO0HzbqdhV/ozNBnlt LTGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=yeoLWBw469H+4eQjfUfs+6P+6/dj2TDSiv3eFST8Fc0=; b=gcgXIsCxnXAhtMANIO4DrK79SC53E2SWr/Vm6DZ8VGvcktwipu4eMKT6zHLu91q+kZ F3KOkk1BqnHP8sV9vsKNjzKKw6IzWPNczhq4aIZ5ZR7dXtBrgvoG+yMDs3gWi4plbziV r5PCHBpT+eoyZ5AudK2x+gRonUoAxvCyqNr4HmPJHREEK9zxiewWe0DSbPy13rFywU1g 5O57SxJnk9jB/LQXovPl4caXcAMxxG421GdUswt7YALKjDMQ2nC+Skn9H3QIB9TNWTMc pW4//w6VTi/8KT1LkzOtvhLJureKP9FwCDDVUsfdVDCMebuF4p36AdIfSU2CyYS2fEJ5 T79Q== X-Gm-Message-State: AOPr4FV54HPY9enMX7GSZA7oR1bZPu47HDL/fzhF6iK7XFkEH2XFpGZM+AaGEbJIv1TdCaJit7CIHdr7xUmJ9Q== X-Received: by 10.182.165.8 with SMTP id yu8mr15904536obb.63.1462203874806; Mon, 02 May 2016 08:44:34 -0700 (PDT) In-Reply-To: <8360uwmq56.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:4003:c01::233 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:203520 Archived-At: --001a11c30c2c8c15b90531ddde51 Content-Type: text/plain; charset=UTF-8 > > 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. > 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. -- -- Kaushal Modi --001a11c30c2c8c15b90531ddde51 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
= The most efficient method is to debug this in C.=C2=A0 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.=C2=A0 Time to
cross that bridge, perhaps?=C2=A0 Here are the instructions in case you
decide to do it:

Just set a breakpoint in Fsignal, and when it breaks, type "bt" t= o
display the backtrace.=C2=A0 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 poi= nter (see below).
=C2=A0
What= improvement did you have in mind?=C2=A0 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=C2= =A0) is corrupted (as of writing this).

If the abo= ve problem is fixed at the time of viewing this email, this is what archive= -contents ended with:=C2=A0

=3D=3D=3D=3D=3D
https://github.com/cosmicexplorer/cloc-emacs") (:keywords "= ;cloc" "count" "source" "code" "lin= es"))]) (clmemo . [(20160326 923) nil "Change Log MEMO" tar = ((:url . "https://github.c= om/ataka/clmemo") (:keywords "convenience"))]) (cljsbuil= d-mode . [(20160402 1000) nil "A minor mode for the ClojureScript '= ;lein cljsbuild' command" single ((:url . "http://github.com/kototama/cljsbuild-mo= de") (:keywords "clojure" "clojurescript" &quo= t;leiningen" "compilation"))]) (cljr-helm . [(20150425 1307)= ((clj-refactor (0 13 0)) (helm (1 5 6))) "Wraps clojure refactor comm= ands with helm" single ((:url . "https://github.com/philjackson/cljr-he
=3D=3D=3D=3D=3D

So the improvement request is if it's possi= ble 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-content= s downloaded from Melpa.
--

--
Kaushal Modi

--001a11c30c2c8c15b90531ddde51--