From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27833 invoked by alias); 31 Aug 2004 15:10:41 -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 27787 invoked from network); 31 Aug 2004 15:10:40 -0000 Received: from unknown (HELO palrel12.hp.com) (156.153.255.237) by sourceware.org with SMTP; 31 Aug 2004 15:10:40 -0000 Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel12.hp.com (Postfix) with ESMTP id 8A42C40230A; Tue, 31 Aug 2004 08:10:36 -0700 (PDT) Received: from napali.hpl.hp.com (napali.hpl.hp.com [15.4.89.123]) by hplms2.hpl.hp.com (8.13.1/8.13.1/HPL-PA Hub) with ESMTP id i7VFAYtP018479; Tue, 31 Aug 2004 08:10:35 -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-3) with ESMTP id i7VFAYEK029052; Tue, 31 Aug 2004 08:10:34 -0700 Received: (from davidm@localhost) by napali.hpl.hp.com (8.12.11/8.12.11/Debian-3) id i7VFAYkm029049; Tue, 31 Aug 2004 08:10:34 -0700 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16692.38122.52348.850833@napali.hpl.hp.com> Date: Tue, 31 Aug 2004 15:10:00 -0000 To: Ulrich Drepper Cc: davidm@hpl.hp.com, libc-hacker@sources.redhat.com, davidm@napali.hpl.hp.com Subject: Re: fix ia64 longjmp() to work from alternate signal-stack In-Reply-To: <412DAC31.1050404@redhat.com> References: <16684.49335.802840.212013@napali.hpl.hp.com> <412DAC31.1050404@redhat.com> Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ X-SW-Source: 2004-08/txt/msg00087.txt.bz2 >>>>> On Thu, 26 Aug 2004 02:24:01 -0700, Ulrich Drepper said: Uli> I don't like this. The behavior of longjmp if the starting point is Uli> using the alternate stack while the destination uses the normal stack, Uli> is currently unspecified in POSIX. I've asked for clarification in the Uli> POSIX working group. The result I expect is "don't do it", aka, Uli> unspecified. Were you able to get clarification on this issue already? Thanks, --david