Re: under gdb: received signal SIG34, Real-time event 34.; received signal SIG35, Real-time event 35

2023-11-14 Thread Adam D Ruppe via Digitalmars-d-learn
On Tuesday, 14 November 2023 at 21:31:39 UTC, mw wrote: handle SIGUSR1 noprint handle SIGUSR2 noprint These are what the GC used to use to stop/start threads. received signal SIG34, Real-time event 34. received signal SIG35, Real-time event 35. And this is what it uses now. druntime just

under gdb: received signal SIG34, Real-time event 34.; received signal SIG35, Real-time event 35

2023-11-14 Thread mw via Digitalmars-d-learn
Hi, I have this in ~/.gdbinit already: ``` handle SIGUSR1 SIGUSR2 nostop handle SIGUSR1 noprint handle SIGUSR2 noprint ``` Today I encountered: received signal SIG34, Real-time event 34. then I added to ~/.gdbinit ``` handle SIG34 nostop noprint pass noignore ``` Next, I got: received