all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>,
	Eli Zaretskii <eliz@gnu.org>
Cc: 17184@debbugs.gnu.org
Subject: bug#17184: 24.3.50; crash while bootstrapping current trunk
Date: Tue, 08 Apr 2014 05:21:55 -0700	[thread overview]
Message-ID: <5343E9E3.7060604@dancol.org> (raw)
In-Reply-To: <87k3b0ukyl.fsf@yahoo.fr>

[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]

On 04/08/2014 04:20 AM, Nicolas Richard wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
> 
>>> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
>>> Date: Fri, 04 Apr 2014 17:26:36 +0200
>>>
>>> So I tried this:
>>> $ gdb --args emacs --batch  -f batch-byte-compile ../lisp/emacs-lisp/tcover-ses.el
>>>
>>> and here's what happens:
>>>
>>> Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:355
>>> 355	  signal (sig, SIG_DFL);
>>>
>>> it aborts because of this in data.c:
>>>   /* Convert to eassert or remove after GC bug is found.  In the
>>>      meantime, check unconditionally, at a slight perf hit.  */
>>>   if (valid_lisp_object_p (definition) < 1)
>>>     emacs_abort ();
>>>
>>> Here's the backtrace:

Interesting. It works for me --- 64- and 32-bit builds. What happens if
you add that Ffset check to emacs-24? What symbol are we trying to set?
(Use xsymbol.) What does valid_lisp_object_p (definition) actually
return when you call it? Can you share your binary and core dump?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-04-08 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 15:26 bug#17184: 24.3.50; crash while bootstrapping current trunk Nicolas Richard
2014-04-04 19:29 ` Eli Zaretskii
2014-04-08 11:20   ` Nicolas Richard
2014-04-08 12:21     ` Daniel Colascione [this message]
2014-04-08 12:54       ` Nicolas Richard
2014-04-08 13:24         ` Daniel Colascione
2014-04-08 13:44           ` Nicolas Richard

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5343E9E3.7060604@dancol.org \
    --to=dancol@dancol.org \
    --cc=17184@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.