unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: koppel@ece.lsu.edu, c.schueller@gmx.at, emacs-devel@gnu.org
Subject: Re: emacs segfault on bootstrap
Date: Mon, 30 Jan 2006 13:46:45 -0500	[thread overview]
Message-ID: <E1F3e33-0004VL-FA@fencepost.gnu.org> (raw)
In-Reply-To: <87psma3l80.fsf@stupidchicken.com> (message from Chong Yidong on Sun, 29 Jan 2006 14:09:03 -0500)

    A cursory inspection did not reveal any bugs in print_object.  Smells
    like a compiler bug.

    Program received signal SIGSEGV, Segmentation fault.
    0x0819c3be in print_object (obj=58, printcharfun=137788457, escapeflag=1)
	at print.c:2009
    2009          switch (XMISCTYPE (obj))
    (gdb) bt
    #0  0x0819c3be in print_object (obj=58, printcharfun=137788457, escapeflag=1)
	at print.c:2009

    (gdb) p obj
    $5 = 137726760
    (gdb) xtype
    Lisp_Int

Do you think that frame 1 mistakenly treated an int
as a vector?

If so, could you look around some more and try to prove it
conclusively?  Try to determine which line did something wrong.
Perhaps you could then easily step through and prove that the
incorrect computation occurs in a certain line or range of lines.

That's all the info needed to make a useful GCC bug report
so that this will get fixed.

  parent reply	other threads:[~2006-01-30 18:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-26 13:10 emacs segfault on bootstrap Clemens Schueller
2006-01-29  5:31 ` cyd
2006-01-29 18:24   ` David Koppelman
2006-01-29 19:09     ` Chong Yidong
2006-01-29 19:22       ` David Koppelman
2006-01-29 19:39       ` Eli Zaretskii
2006-01-29 19:50         ` David Koppelman
2006-01-30  4:19           ` Eli Zaretskii
2006-01-30 18:46       ` Richard M. Stallman [this message]
2006-02-01 18:40     ` Clemens Schueller
2006-02-03  5:03       ` Richard M. Stallman

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=E1F3e33-0004VL-FA@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=c.schueller@gmx.at \
    --cc=emacs-devel@gnu.org \
    --cc=koppel@ece.lsu.edu \
    /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).