From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28494 invoked by alias); 19 Apr 2004 18:39:49 -0000 Mailing-List: contact libc-hacker-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-hacker-owner@sources.redhat.com Received: (qmail 28478 invoked from network); 19 Apr 2004 18:39:49 -0000 Received: from unknown (HELO palrel13.hp.com) (156.153.255.238) by sources.redhat.com with SMTP; 19 Apr 2004 18:39:49 -0000 Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel13.hp.com (Postfix) with ESMTP id E91721C00ED1 for ; Mon, 19 Apr 2004 11:39:48 -0700 (PDT) Received: from napali.hpl.hp.com (napali.hpl.hp.com [15.4.89.123]) by hplms2.hpl.hp.com (8.12.10/8.12.10/HPL-PA Hub) with ESMTP id i3JIdl7s003042 for ; Mon, 19 Apr 2004 11:39:47 -0700 (PDT) Received: from napali.hpl.hp.com (napali [127.0.0.1]) by napali.hpl.hp.com (8.12.11/8.12.11/Debian-1) with ESMTP id i3JIdkEh011495; Mon, 19 Apr 2004 11:39:46 -0700 Received: (from davidm@localhost) by napali.hpl.hp.com (8.12.11/8.12.11/Debian-1) id i3JIdk17011491; Mon, 19 Apr 2004 11:39:46 -0700 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16516.7410.677626.450899@napali.hpl.hp.com> Date: Mon, 19 Apr 2004 18:39:00 -0000 To: libc-hacker@sources.redhat.com Cc: davidm@napali.hpl.hp.com Subject: what to do about dl_iterate_phdr() In-Reply-To: <16492.44824.546092.273252@napali.hpl.hp.com> References: <16491.51649.225477.81600@napali.hpl.hp.com> <200404012122.i31LM3sg027149@magilla.sf.frob.com> <16492.44824.546092.273252@napali.hpl.hp.com> Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ X-SW-Source: 2004-04/txt/msg00061.txt.bz2 dl_iterate_phdr() isn't signal-safe and therefore there is currently no way to safely unwind out of a signal-handler. My proposal to make dl_iterate_phdr() async-signal-safe seems to have fallen on deaf ears. So what's your position? Is the official position that glibc simply cannot safely unwind out of a signal handler or do you have an alternate proposal in mind? Thanks, --david