[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 07:37:04 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) |
Barry OReilly <gundaetiapo@gmail.com> 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?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- bug#15794: Core dump after SIGTERM during GC marking, Barry OReilly, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking,
Andreas Schwab <=
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Barry OReilly, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/03
- bug#15794: Core dump after SIGTERM during GC marking, Andreas Schwab, 2013/11/04
- bug#15794: Core dump after SIGTERM during GC marking, Eli Zaretskii, 2013/11/04