GNU bug report logs - #7098
Emacs24 crash with segmentation fault

Previous Next

Full log

Message #143 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#7098: Emacs24 crash with segmentation fault
Date: Tue, 21 Dec 2010 12:34:38 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Thierry Volpiatto <thierry.volpiatto <at> gmail.com>
>> Date: Sat, 18 Dec 2010 10:16:10 +0100
>> Cc: 
>> 
>> First crash since yesterday when closing w3m:
>> 
>> Program received signal SIGSEGV, Segmentation fault.
>> 0x081903b7 in mark_object (arg=172893790) at alloc.c:5577
>> 5577          FLOAT_MARK (XFLOAT (obj));
>
> Ouch!

yes!

>> (gdb) bt full
>> #0  0x081903b7 in mark_object (arg=172893790) at alloc.c:5577
>>         obj = <value optimized out>
>
> How come values are "optimized out" when you compiled without
> optimizations?  Can you show a sample GCC compilation command line
> from the build process, with all its switches?
>
> Also, please type "source /path/to/src/.gdbinit" at GDB's prompt
> (where "/path/to/src/" is the Emacs src directory), and then type
> "xbacktrace", to show the Lisp-level backtrace.

Sorry, i have not the time actually to try to debug that, i have
switched back to 23.2.91 that is stable, no crash.
Maybe you could try to see why 23.2.* is stable and 24 is not.
And what is wrong in alloc.c?

-- 
A+ Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997 

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.