GNU bug report logs - #15794
Core dump after SIGTERM during GC marking

Previous Next

Package: emacs;

Reported by: Barry OReilly <gundaetiapo <at> gmail.com>

Date: Sun, 3 Nov 2013 04:30:03 UTC

Severity: normal

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Andreas Schwab <schwab <at> linux-m68k.org>
To: Barry OReilly <gundaetiapo <at> gmail.com>
Cc: 15794 <at> debbugs.gnu.org
Subject: bug#15794: Core dump after SIGTERM during GC marking
Date: Sun, 03 Nov 2013 07:37:04 +0100

Barry OReilly <gundaetiapo <at> 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 <at> linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
This bug report was last modified 5 years and 289 days ago.

Previous Next

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