From owner-freebsd-ppc@FreeBSD.ORG Sat Oct 19 06:38:12 2013 Return-Path: Delivered-To: ppc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 567456F1 for ; Sat, 19 Oct 2013 06:38:12 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB938294D for ; Sat, 19 Oct 2013 06:38:11 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.7/8.14.7) with ESMTP id r9J6c2sh061494; Sat, 19 Oct 2013 09:38:02 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.8.3 kib.kiev.ua r9J6c2sh061494 Received: (from kostik@localhost) by tom.home (8.14.7/8.14.7/Submit) id r9J6c1DY061493; Sat, 19 Oct 2013 09:38:01 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 19 Oct 2013 09:38:01 +0300 From: Konstantin Belousov To: Julio Merino Subject: Re: powerpc/183040: Nested signal handling is broken Message-ID: <20131019063801.GK3865@kib.kiev.ua> References: <201310162349.r9GNnDud012497@mastodon.meroh.net> <20131017073158.GB3865@kib.kiev.ua> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RnxXMyWEPIZsopkG" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on tom.home Cc: ppc@freebsd.org X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Oct 2013 06:38:12 -0000 --RnxXMyWEPIZsopkG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 18, 2013 at 04:07:30PM -0400, Julio Merino wrote: > On Thu, Oct 17, 2013 at 3:31 AM, Konstantin Belousov > wrote: > > What you could do, is to localize the point where the breakage occur. > > Add a function like this: > > > > static void > > print_sig_disposition(int signo) > > { > > struct sigaction sa; > > sigaction(signo, NULL, &sa); > > printf("sig %d handler %p\n", signo, sa.sa_handler); > > } > > > > and sprinkle a calls to it often enough, to see where the reset of the > > disposition happens. Insert the call to the function into the signal > > handler as well. >=20 > As far as I can tell, the sa_handler remains set all the time. It's > correct before the call to kill(). Please provide the modified test program and its exact output. --RnxXMyWEPIZsopkG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBAgAGBQJSYijIAAoJEJDCuSvBvK1BKPcP/3lBzQb52yLNxXTwPL2SqGS/ eY61Tf3WjkYrd6oryX2o5rgKKsiAsoxbHiVtytYuDV891ovNc1n8U4xiOStVFHsz ZXXc3mLyhi6tJBgHEPKqwkGaDhwlFraIOsXuYZpFdoz55REosCI9Q7Umy907/bIm 6S1o4/bcaIt1C/TXbSONN4hbM/vHx3II06n4UAclGfZR8urA+jTBaohu098QwC06 LmjRPoSdcCaljX2JLVrlZNGE4Hv58u6R0xg+FbbtcK30/VjSkUchYX+WFy2oxj0k gdtPJCv2OBVALS7X50IE8gzUYBPoX049dB2QLoG0vfx9HhytgJ+RN0+bVFb52bIX sddhUrThTV/3rb5i91KZjr/53XFYvwXHfXnTafu72NkIZsdQLcMPYTbMCAcozBTX Dc33tvI7Sd9olFi56RMULnKdFJB0vq03+lUaWNNGHJEsYkj5JhSgA7ZlwM/CE2X3 95P0tfEAmh3NpMYAhLCSWobujbP71LuSTLznfKSIqZnwc2wb0M7aLHbjizGGARuz zrCVLV6JjdmPpwpMKjQtaDNWYft486Qe2wzcC/15yfWrBCymlhRHRSZKqb6QJXQu iEptxVDl3HR1x4MB9qA4jAbSpwUlhKXSyowMippkNYe8TuUH/9JMqAnuNfi/d/L3 Z6EuOmVh3M6l7bhg1NUa =Nl1C -----END PGP SIGNATURE----- --RnxXMyWEPIZsopkG--