digitalmars.D.learn - under gdb: received signal SIG34, Real-time event 34.; received signal
- mw (19/19) Nov 14 2023 Hi,
- Adam D Ruppe (5/9) Nov 14 2023 And this is what it uses now.
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 signal SIG35, Real-time event 35. I'm wondering why? and how many more such SIG<xx> I should put into ~/.gdbinit? BTW, I'm using LDC2 1.34.0 Thanks.
Nov 14 2023
On Tuesday, 14 November 2023 at 21:31:39 UTC, mw wrote:handle SIGUSR1 noprint handle SIGUSR2 noprintThese 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 replaced usr1/2 with rt34/35 to lessen the likelyhood of conflicts with other libraries.
Nov 14 2023