unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: karl@freefriends.org (Karl Berry)
Cc: 9713@debbugs.gnu.org
Subject: bug#9713: emacs 24.0.90 alloc.c assertion failure
Date: Mon, 10 Oct 2011 01:45:14 -0400	[thread overview]
Message-ID: <E1RD8fq-0002YG-BS@fencepost.gnu.org> (raw)
In-Reply-To: <201110100021.p9A0LN4m013541@freefriends.org> (karl@freefriends.org)

> Date: Mon, 10 Oct 2011 00:21:23 GMT
> From: karl@freefriends.org (Karl Berry)
> 
> (If there's a different place to report pretest bugs, please inform.
> Saw nothing in the README.)

This is the right place.  "M-x report-emacs-bug RET" does TRT
automagically.

> Trying to compile the emacs 24.0.90 pretest on (the latest) CentOS 5.7,
> the assertion at line 740 of alloc.c fails:
> verify (INT_MAX <= PTRDIFF_MAX);
> 
> With the system compiler (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)),
> the error is;
> alloc.c:740: error: negative width in bit-field '_gl_verify_error_if_negative'
> 
> With gcc 4.6.1 compiled from the original sources, the error is:
> alloc.c:740:1: error: static assertion failed: "verify (INT_MAX <= PTRDIFF_MAX)"

What are INT_MAX and PTRDIFF_MAX on that machine?  IOW, first let's
see if this is a false alarm or not.





  reply	other threads:[~2011-10-10  5:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-10  0:21 bug#9713: emacs 24.0.90 alloc.c assertion failure Karl Berry
2011-10-10  5:45 ` Eli Zaretskii [this message]
2011-10-10 18:28   ` Glenn Morris
2011-10-11 17:55     ` Karl Berry
2011-10-11 19:29       ` Eli Zaretskii
2011-10-11 20:17         ` Glenn Morris
2011-10-11 22:07           ` Eli Zaretskii
2011-10-11 22:13             ` Karl Berry
2011-10-11 23:09               ` Glenn Morris
     [not found] ` <50158261@toto.iv>
2011-10-11 23:52   ` bug#9713: stdint.h in emacs Karl Berry
2011-10-12  0:13     ` Glenn Morris
2011-10-13 18:54       ` Karl Berry
2011-10-12  7:07     ` Paul Eggert

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=E1RD8fq-0002YG-BS@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=9713@debbugs.gnu.org \
    --cc=karl@freefriends.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).