From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61184 invoked by alias); 21 Oct 2016 18:52:35 -0000 Mailing-List: contact gnu-gabi-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Post: List-Help: List-Subscribe: Sender: gnu-gabi-owner@sourceware.org Received: (qmail 61166 invoked by uid 89); 21 Oct 2016 18:52:34 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Checked: by ClamAV 0.99.2 on sourceware.org X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:692 X-Spam-Status: No, score=-2.2 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org X-Spam-Level: X-HELO: mx1.redhat.com Subject: Re: [PATCH] Make _Unwind_GetIPInfo part of the ABI To: "H.J. Lu" References: Cc: Michael Matz , gnu-gabi@sourceware.org From: Florian Weimer Message-ID: <82ccf018-3384-2c3a-be3e-af7e171c2006@redhat.com> Date: Fri, 01 Jan 2016 00:00:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.38]); Fri, 21 Oct 2016 18:52:33 +0000 (UTC) X-SW-Source: 2016-q4/txt/msg00021.txt.bz2 On 10/21/2016 08:37 PM, H.J. Lu wrote: >> It's not really clear to me how the glibc unwinders tell traps from faults. (I meant to write “gcc unwinders”.) > We can set signal_frame to 0 for SIGCANCEL? No, SIGCANCEL is a signal frame for all intents in purposes. (The bug was that __gcc_personality_v0 (the C unwinder) completely ignored signal frame hints on all architectures.) The question if INTO should result in a signal frame. Per Michael's comments, it should not because it is a trap and gets reported at the immediately following address (which can be in a completely different exception handling region). Thanks, Florian