From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12178 invoked by alias); 9 Jun 2019 15:43:10 -0000 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 Received: (qmail 12169 invoked by uid 89); 9 Jun 2019 15:43:09 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS autolearn=ham version=3.3.1 spammy= X-HELO: gateway21.websitewelcome.com Received: from gateway21.websitewelcome.com (HELO gateway21.websitewelcome.com) (192.185.45.159) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 09 Jun 2019 15:43:08 +0000 Received: from cm10.websitewelcome.com (cm10.websitewelcome.com [100.42.49.4]) by gateway21.websitewelcome.com (Postfix) with ESMTP id 6A9DC400C4DC3 for ; Sun, 9 Jun 2019 10:43:07 -0500 (CDT) Received: from box5379.bluehost.com ([162.241.216.53]) by cmsmtp with SMTP id ZzyNhdf6I2PzOZzyNhwyYs; Sun, 09 Jun 2019 10:43:07 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tromey.com; s=default; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=uKcpkLB5uKK3KUbdCoNsx8Pe9qUH0ZyUUCWplbpn/PI=; b=ff/Agz4Aoku/7CR8bPm0gdFILn T/Iz2wmyqVyAXi0CkBHOOJiVZ2AePbAkXiP0Hee2IJfVLVN3NHemz6ycX42hfF+Wr7JHtop6bA1uo vj9qNjD8k+wNu6tMfTP9WZMQy; Received: from 174-29-48-168.hlrn.qwest.net ([174.29.48.168]:55414 helo=bapiya) by box5379.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1hZzyN-002yLl-5p; Sun, 09 Jun 2019 10:43:07 -0500 From: Tom Tromey To: Pedro Alves Cc: Tom Tromey , gdb-patches@sourceware.org Subject: Re: [PATCH v3 6/8] Introduce thread-safe way to handle SIGSEGV References: <20190529212916.23721-1-tom@tromey.com> <20190529212916.23721-7-tom@tromey.com> Date: Sun, 09 Jun 2019 15:43:00 -0000 In-Reply-To: (Pedro Alves's message of "Thu, 30 May 2019 14:40:36 +0100") Message-ID: <87y32aaho5.fsf@tromey.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2019-06/txt/msg00189.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: >> + signal (sig, handle_sigsegv); Pedro> Doesn't this lose the SA_ONSTACK? Yeah. I'm glad you caught this since it points out that we have to call sigaltstack per-thread. Tom