|
From: | Amirouche Boubekki |
Subject: | Re: Thread 1 "guile" received signal SIGPWR, Power fail/restart. |
Date: | Sun, 21 Jan 2018 11:24:23 +0100 |
User-agent: | Roundcube Webmail/1.1.2 |
On 2018-01-21 05:45, Mark H Weaver wrote:
Amirouche Boubekki <address@hidden> writes:I have a guile crash that I can reproduce all the time so far that says:Thread 1 "guile" received signal SIGPWR, Power fail/restart.SIGPWR is used internally by libgc. If I recall correctly, it's done tosuspend all threads within their signal handlers before performing a garbage collection. I can't seem to reproduce this on my system at the moment, but as I recall, when this happened in GDB I would simply type "c" to continue. Does that work for you? Mark
Indeed: Thread 1 "guile" received signal SIGPWR, Power fail/restart.0x00007ffff762b58f in pthread_cond_wait@@GLIBC_2.3.2 () from /gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25/lib/libpthread.so.0
(gdb) c Continuing. Thread 1 "guile" received signal SIGXCPU, CPU time limit exceeded.0x00007ffff5f386a6 in sigsuspend () from /gnu/store/3h31zsqxjjg52da5gp3qmhkh4x8klhah-glibc-2.25/lib/libc.so.6
(gdb) c Continuing. [New Thread 0x7fffed9f1700 (LWP 27311)] [Thread 0x7fffee1f2700 (LWP 27293) exited] Thanks Mark!
[Prev in Thread] | Current Thread | [Next in Thread] |