From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: [emacs-announce] Emacs pretest 25.0.93
Date: Sat, 23 Apr 2016 16:48:47 +0300 [thread overview]
Message-ID: <83zisk4erk.fsf@gnu.org> (raw)
In-Reply-To: <87vb38o3ll.fsf@Rainer.invalid> (message from Achim Gratz on Sat, 23 Apr 2016 15:29:42 +0200)
> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Sat, 23 Apr 2016 15:29:42 +0200
>
> Eli Zaretskii writes:
> > Run the faulting command under a debugger, put a breakpoint in
> > Fsignal, and show the backtrace. That might produce enough hints to
> > find out what is failing and why.
>
> It doesn't really fault, at least not at the lisp level.
Fsignal is on the C level, so a breakpoint set there in GDB will catch
any error.
> There actually is an auto-save file that seems to have all the
> extracted loaddefs in, but somehow it then doesn't finish. For the
> autoloads entries there are lots of differences like these (I'm
> comparing with the installed version of my last build):
>
> -;;;### (autoloads nil "cal-iso" "cal-iso.el" t)
> +;;;### (autoloads nil "cal-iso" "cal-iso.el" (22225 49314 854982
> +;;;;;; 791000))
AFAIU, these differences are meaningless. But I have no autoloads
whose time stamp is 't'.
The problem is still the error that is signaled, and the way to
investigate it is to figure out why the error is signaled.
next prev parent reply other threads:[~2016-04-23 13:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 17:26 [emacs-announce] Emacs pretest 25.0.93 Nicolas Petton
2016-04-22 17:52 ` Philipp Stephani
2016-04-22 18:58 ` Eli Zaretskii
2016-04-22 19:08 ` nicolas
2016-04-22 19:12 ` Nicolas Petton
2016-04-22 19:58 ` Eli Zaretskii
2016-04-23 11:41 ` Achim Gratz
2016-04-23 12:05 ` Eli Zaretskii
2016-04-23 12:28 ` Achim Gratz
2016-04-23 12:37 ` Achim Gratz
2016-04-23 12:51 ` Eli Zaretskii
2016-04-23 13:29 ` Achim Gratz
2016-04-23 13:48 ` Eli Zaretskii [this message]
2016-04-23 15:20 ` Michael Heerdegen
2016-04-23 16:55 ` Achim Gratz
2016-04-23 17:23 ` Michael Heerdegen
2016-04-23 17:59 ` Eli Zaretskii
2016-04-23 18:11 ` Achim Gratz
2016-04-23 22:19 ` Michael Heerdegen
2016-04-24 5:56 ` Eli Zaretskii
2016-04-24 6:22 ` Achim Gratz
2016-04-23 17:39 ` Glenn Morris
2016-04-23 17:54 ` Achim Gratz
2016-04-23 18:46 ` Glenn Morris
2016-04-23 12:52 ` [emacs-announce] " Eli Zaretskii
2016-04-25 10:09 ` Phillip Lord
2016-04-25 10:21 ` Eli Zaretskii
2016-04-25 13:25 ` Chris Zheng
2016-04-26 5:45 ` Eli Zaretskii
2016-04-26 16:49 ` Phillip Lord
2016-04-26 17:26 ` Eli Zaretskii
2016-04-26 17:45 ` Phillip Lord
2016-04-26 18:29 ` Eli Zaretskii
2016-04-26 19:09 ` Kaushal Modi
2016-04-26 19:14 ` Eli Zaretskii
2016-04-26 19:28 ` Kaushal Modi
2016-04-26 19:32 ` Stephen Leake
2016-04-26 19:40 ` Eli Zaretskii
2016-04-26 22:32 ` Phillip Lord
2016-04-27 7:25 ` Eli Zaretskii
2016-04-30 9:57 ` Eli Zaretskii
2016-04-25 22:30 ` Phillip Lord
2016-04-26 13:43 ` Eli Zaretskii
2016-04-26 13:57 ` Kaushal Modi
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=83zisk4erk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@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).