> From: Mark H Weaver
> Date: Sat, 20 Jan 2018 23:45:54 -0500
> Cc: Guile Devel
>
> SIGPWR is used internally by libgc. If I recall correctly, it's done to
> suspend all threads within their signal handlers before performing a
> garbage collection. I can't seem to reproduce this on my system a
On 2018-01-21 05:45, Mark H Weaver wrote:
Amirouche Boubekki 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 do
Amirouche Boubekki 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 to
suspend all threads with
On 2018-01-20 20:48, Amirouche Boubekki wrote:
On 2018-01-20 20:32, Amirouche Boubekki wrote:
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.
[snip]
The core is at http://hyperdev.fr/sta
On 2018-01-20 20:32, Amirouche Boubekki wrote:
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.
I can reproduce the bug without guile-wiredtiger, here is the backtrace:
[Thread 0x7fffed9f1700
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.
Before the crash I see things like that when running with guile with
gdb:
[Thread 0x7fffe3fff700 (LWP 24262) exited]
[New Thread 0x7fffea8
