From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13839 invoked by alias); 23 Aug 2012 17:18:52 -0000 Received: (qmail 13822 invoked by uid 22791); 23 Aug 2012 17:18:51 -0000 X-SWARE-Spam-Status: No, hits=-8.7 required=5.0 tests=AWL,BAYES_00,KHOP_PGP_SIGNED,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.gentoo.org (HELO smtp.gentoo.org) (140.211.166.183) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 17:18:37 +0000 Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id BC05A33E07F; Thu, 23 Aug 2012 17:18:36 +0000 (UTC) From: Mike Frysinger To: Pedro Alves Subject: Re: further improve "handle" help string Date: Thu, 23 Aug 2012 17:18:00 -0000 User-Agent: KMail/1.13.7 (Linux/3.5.0; KDE/4.6.5; x86_64; ; ) Cc: Eli Zaretskii , Doug Evans , gdb-patches@sourceware.org References: <1344704080-24677-1-git-send-email-vapier@gentoo.org> <201208142158.42487.vapier@gentoo.org> <503659B8.9020107@redhat.com> In-Reply-To: <503659B8.9020107@redhat.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart5723424.VD8DzvZZcx"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201208231318.36988.vapier@gentoo.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-08/txt/msg00679.txt.bz2 --nextPart5723424.VD8DzvZZcx Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-length: 1725 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=20 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 --nextPart5723424.VD8DzvZZcx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. Content-length: 836 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJQNmXsAAoJEEFjO5/oN/WBET4QAN6lZrYRBZXoLpd9S+Rf9jce VpoxyGFrHbEDaVwMGK1wYBigDzlv5oRxuj9Mixzd4TdM48Ay805Or0rMLfSXUJ6f xO55Gbtv/kyo0g6juXZnSbueVpQGfYZD+ta5iprQENQIUvLazuLwxi4rsGUEB8Ml x7p4wW+PxfeNv3ALbQZoHGUirgQRzkblSxwcQ9g9i9J6rlWG1N4hOhRHciOx0n2J kdw5NTSrnQPUayaN/K6vt6MBUaNTYzFb0AHduUJxgqmdSQN7uwaPQFyNsMScSeW9 w4ZZMNs0NGujrZm/LXRAEcTtmrSheJeBu/dRoQzHCGuKkL/fwNKX9rJl4UeUbVBm /cOMukdF/LmofdEaVhUsLp95+s/y/6e0H/+jeXH7W0ifM5W3z+gL8pDMp/d41BSf Wo3R1m9EGHMUcMk0DxOdzcVfea/wylFpjTYUn2a78S/L+1G4Qzp3oex7buDmRFcb CdqBHj7q8erDfTQKp+FNKSXUrPKaQiFTWcePcc1Q4DZr5x7i7JdqkZ+TuzKpiwxf UpAQ8SGChQD0sS/Plk6y62Hrf3WavQoNwPQSyot6Im7bsPe/Xwhq3TVzE4ezi7qg gwwuk4OcA6idSBU1xggPhWMXdizjwabzgBzGArYyOL+62qT1xuz6zzz+iRfx3VaG feFFnbd4u8yAJIRZ/Gun =vl2T -----END PGP SIGNATURE----- --nextPart5723424.VD8DzvZZcx--