Printing diagnostics via SIGUSR2 not showing callstack

ID:97144
 
Jun 19 2010, 4:09 pm
BYOND Version:470
Operating System:FreeBSD
Web Browser:
Applies to:Dream Daemon
Status: Unverified
Thus far we've been unable to verify or reproduce this bug. Or, it has been observed but it cannot be triggered with a reliable test case. You can help us out by editing your report or adding a comment with more information.
I am uncertain of this, but when Dream Daemon starts suppressing proc crash messages as such:

Warning: further proc crash messages are being suppressed to prevent overload...

I suspect that when using SIGUSR2 to print diagnostics it prevents the callstack from being printed out as well.

I'll test this further when I can but I'm pretty sure this is the case.
Jun 29 2010, 3:26 pm
It doesn't look to be setup this way in the code (the callstack is suppressed on proc crashes when there are >=20 prior runtime errors, but not via the manual USR2 signal). It's a bit hard to test because of the way the procs are traced.

If you can provide more info or can give us a demo to test, that'd help.