bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#15794: Core dump after SIGTERM during GC marking


From: Andreas Schwab
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 19:03:00 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)

Eli Zaretskii <address@hidden> writes:

>> From: Andreas Schwab <address@hidden>
>> Date: Sun, 03 Nov 2013 07:37:04 +0100
>> Cc: address@hidden
>> 
>> Barry OReilly <address@hidden> writes:
>> 
>> > #60 0x00000000004ecaa5 in deliver_process_signal (sig=15, handler=0x4ebc30 
>> > <handle_fatal_signal>) at sysdep.c:1597
>> >         old_errno = 11
>> >         on_main_thread = true
>> > #61 <signal handler called>
>> > No symbol table info available.
>> > #62 string_intervals (s=57280353) at lisp.h:3129
>> > No locals.
>> > #63 mark_object (arg=<optimized out>) at alloc.c:5957
>> >         ptr = <optimized out>
>> >         ptrx = <optimized out>
>> >         obj = 59121106
>> >         cdr_count = 0
>> 
>> The signal was received during GC.  Shouldn't its handling be postponed
>> then?
>
> Maybe.  But then it would be impossible to kill Emacs during a runaway
> GC in a way that would cause Emacs to auto-save, wouldn't it?

Even auto-save is a no-no in a signal handler.

Andreas.

-- 
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."





reply via email to

[Prev in Thread] Current Thread [Next in Thread]