Use 'SIGUSR2' signal instead of 'SIGUSR1' to stop debugged processes, because 'SIGUSR1' makes WebKit crash.
[GB.DEBUG] * BUG: Use 'SIGUSR2' signal instead of 'SIGUSR1' to stop debugged processes, because 'SIGUSR1' makes WebKit crash.
This commit is contained in:
parent
7c87764c29
commit
5bcecf2c41
1 changed files with 3 additions and 3 deletions
|
@ -99,10 +99,10 @@ void DEBUG_break_on_next_line(void)
|
|||
|
||||
static void signal_user(int sig)
|
||||
{
|
||||
signal(SIGUSR1, signal_user);
|
||||
signal(SIGUSR2, signal_user);
|
||||
|
||||
#ifdef DEBUG_ME
|
||||
fprintf(stderr, "Got SIGUSR1\n");
|
||||
fprintf(stderr, "Got SIGUSR2\n");
|
||||
#endif
|
||||
|
||||
/*CAPP_got_signal();*/
|
||||
|
@ -267,7 +267,7 @@ DEBUG_INFO *DEBUG_init(GB_DEBUG_INTERFACE *debug, bool fifo, const char *fifo_na
|
|||
|
||||
//ARRAY_create(&_breakpoints);
|
||||
GB.NewArray(&_breakpoints, sizeof(DEBUG_BREAK), 16);
|
||||
signal(SIGUSR1, signal_user);
|
||||
signal(SIGUSR2, signal_user);
|
||||
signal(SIGPIPE, SIG_IGN);
|
||||
|
||||
setlinebuf(_out);
|
||||
|
|
Loading…
Reference in a new issue