unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: cvs head crash in GC
Date: Sun, 13 Apr 2003 07:24:03 -0400	[thread overview]
Message-ID: <E194fad-0006PR-00@fencepost.gnu.org> (raw)
In-Reply-To: <m3el4njc87.fsf@loiso.podval.org> (message from Sam Steingold on 31 Mar 2003 19:24:56 -0500)

    Program received signal SIGSEGV, Segmentation fault.
    0x4207a8d5 in bcopy () from /lib/tls/libc.so.6
    (gdb) where
    #0  0x4207a8d5 in bcopy () from /lib/tls/libc.so.6
    #1  0x0804feee in safe_bcopy (from=0x99390cc "\2649o\b", 
	to=0x99b4458 "\324y\316\bnnimap+mail.podval.org:.imap/lisp/misc", 
	size=504716) at dispnew.c:484
    #2  0x0811c7e1 in compact_small_strings () at alloc.c:1641

It is clear that the size argument to safe_bcopy is nonsense.
A string 504716 bytes long would not be stored in "small string"
fashion.

The next step is to figure out the chain of events that occurred
in compact_small_strings.  The value that you got for FROM seems
impossible--it does not match the FROM arg in safe_bcopy.
I think that the variable FROM is not live at that point,
and its register is in use for something else or was not saved.
You can assume FROM was actually 0x99390cc.  It would be interesting
to cross-check that  against the value of FROM_END.

Please look at FROM->string; that is the Lisp_String structure.
What is in that?

      parent reply	other threads:[~2003-04-13 11:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-01  0:24 cvs head crash in GC Sam Steingold
2003-04-01  4:27 ` Eli Zaretskii
2003-04-01  7:15   ` Juanma Barranquero
     [not found]     ` <1049186003.3e894ed395735@webmail.freedom2surf.net>
2003-04-01 19:01       ` Eli Zaretskii
2003-04-01 12:44   ` Andreas Schwab
2003-04-01 13:21     ` Juanma Barranquero
2003-04-01 13:33       ` Andreas Schwab
2003-04-01 13:36         ` Juanma Barranquero
2003-04-13 11:24 ` Richard Stallman [this message]

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=E194fad-0006PR-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).