This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thursday 23 August 2012 12:26:32 Pedro Alves wrote: > Multiple signals may be specified. Signal numbers and signal names > may be interspersed with actions, with the actions being performed for > all signals cumulatively specified. this doesn't accurately describe real world behavior (but maybe that's a bug?). this is why i avoided that aspect in the first place :(. for example: (gdb) handle SIGHUP SIGUSR1 SIGUSR2 SIGPWR Signal Stop Print Pass to program Description SIGHUP Yes Yes Yes Hangup SIGUSR1 Yes Yes Yes User defined signal 1 SIGUSR2 Yes Yes Yes User defined signal 2 SIGPWR Yes Yes Yes Power fail/restart (gdb) handle SIGHUP SIGUSR1 SIGUSR2 nostop SIGPWR Signal Stop Print Pass to program Description SIGHUP No Yes Yes Hangup SIGUSR1 No Yes Yes User defined signal 1 SIGUSR2 No Yes Yes User defined signal 2 SIGPWR Yes Yes Yes Power fail/restart (gdb) handle SIGPWR Signal Stop Print Pass to program Description SIGPWR Yes Yes Yes Power fail/restart (gdb) handle SIGHUP SIGUSR1 SIGUSR2 SIGPWR nostop Signal Stop Print Pass to program Description SIGHUP No Yes Yes Hangup SIGUSR1 No Yes Yes User defined signal 1 SIGUSR2 No Yes Yes User defined signal 2 SIGPWR No Yes Yes Power fail/restart so saying "all signals cumulatively" is not how the code is behaving. -mike
Attachment:
signature.asc
Description: This is a digitally signed message part.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |