From: Kenichi Handa <handa@m17n.org>
Cc: nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: Emacs crashes
Date: Tue, 14 Mar 2006 09:39:38 +0900 [thread overview]
Message-ID: <E1FIxZa-0006Zm-00@etlken> (raw)
In-Reply-To: <m3pskqrod2.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
In article <m3pskqrod2.fsf@kfs-l.imdomain.dk>, storm@cua.dk (Kim F. Storm) writes:
> I haven't seen any of these -- so there are now 6 different crashes.
> Looks like a completely random memory corruption.
Yesterday, I met Emacs crash this way:
Program received signal SIGSEGV, Segmentation fault.
0x40359560 in mallopt () from /lib/libc.so.6
(gdb) bt 10
#0 0x40359560 in mallopt () from /lib/libc.so.6
#1 0x4035a339 in mallopt () from /lib/libc.so.6
#2 0x08138341 in emacs_blocked_malloc (size=1078031196, ptr=0x8137cad)
at alloc.c:1217
#3 0x40357f55 in malloc () from /lib/libc.so.6
#4 0x08137cad in xmalloc (size=140991128) at alloc.c:740
#5 0x0809c8a8 in coding_allocate_composition_data (coding=0x89c41c8,
char_offset=1078031196) at coding.c:1708
#6 0x080a5d17 in decode_coding_string (str=151149291, coding=0x10, nocopy=0)
at coding.c:6294
#7 0x08182865 in read_process_output (proc=144453228, channel=46)
at process.c:5040
(gdb) up 5
#5 0x0809c8a8 in coding_allocate_composition_data (coding=0x89c41c8,
char_offset=1078031196) at coding.c:1708
1708 = (struct composition_data *) xmalloc (sizeof *cmp_data);
But, this Emacs was compiled before these changes:
2006-03-10 Kim F. Storm <storm@cua.dk>
* alloc.c (USE_POSIX_MEMALIGN): Fix last change.
2006-03-09 Stefan Monnier <monnier@iro.umontreal.ca>
* alloc.c (USE_POSIX_MEMALIGN): New macro.
(ABLOCKS_BASE, lisp_align_malloc, lisp_align_free): Use it.
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2006-03-14 0:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:23 Emacs crashes Nick Roberts
2006-03-13 20:47 ` Chong Yidong
2006-03-13 22:06 ` Kim F. Storm
2006-03-14 0:39 ` Kenichi Handa [this message]
2006-03-14 16:09 ` Richard Stallman
2006-03-15 3:24 ` Giorgos Keramidas
2006-03-15 20:23 ` Richard Stallman
2006-03-14 1:02 ` Juanma Barranquero
2006-03-14 9:36 ` David Kastrup
2006-03-14 11:59 ` Juanma Barranquero
2006-03-14 17:45 ` Richard Stallman
2006-03-15 8:58 ` Juanma Barranquero
2006-03-17 16:32 ` Richard Stallman
2006-03-17 16:41 ` Juanma Barranquero
2006-03-14 1:37 ` Nick Roberts
2006-03-14 16:07 ` Chong Yidong
2006-03-14 16:15 ` Kim F. Storm
2006-03-14 16:09 ` Richard Stallman
2006-03-14 20:47 ` Kim F. Storm
2006-03-14 21:35 ` Chong Yidong
2006-03-15 20:21 ` Richard Stallman
2006-03-14 22:38 ` Kim F. Storm
2006-03-15 9:22 ` Nick Roberts
2006-03-15 9:28 ` David Kastrup
2006-03-15 11:35 ` Jan D.
2006-03-15 3:21 ` Giorgos Keramidas
2006-03-15 20:21 ` Richard Stallman
2006-03-15 15:41 ` Kim F. Storm
2006-03-15 17:05 ` Luc Teirlinck
2006-03-15 17:21 ` Chong Yidong
2006-03-15 19:03 ` Kim F. Storm
2006-03-15 21:40 ` Nick Roberts
2006-03-14 4:33 ` Eli Zaretskii
2006-03-14 20:45 ` Nick Roberts
2006-03-15 4:43 ` Eli Zaretskii
2006-03-15 7:49 ` Nick Roberts
2006-03-15 19:49 ` Eli Zaretskii
2006-03-15 21:40 ` Nick Roberts
2006-03-16 20:18 ` Richard Stallman
2006-03-16 21:25 ` Nick Roberts
2006-03-18 14:31 ` Eli Zaretskii
2006-03-15 20:21 ` Richard Stallman
2006-03-16 20:18 ` Richard 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=E1FIxZa-0006Zm-00@etlken \
--to=handa@m17n.org \
--cc=emacs-devel@gnu.org \
--cc=nickrob@snap.net.nz \
/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).