From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: MPS: a random backtrace while toying with gdb Date: Mon, 01 Jul 2024 17:42:27 +0000 Message-ID: <87jzi580vw.fsf@localhost> References: <87bk3jh8bt.fsf@localhost> <86le2mhhsj.fsf@gnu.org> <875xtqramd.fsf@gmail.com> <86cynyhfsn.fsf@gnu.org> <87v81qp91g.fsf@gmail.com> <86r0cefb0i.fsf@gnu.org> <86msn1fk0c.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2068"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , eller.helmut@gmail.com, gerd.moellmann@gmail.com, emacs-devel@gnu.org To: Pip Cet Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jul 01 19:41:32 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sOL1w-0000Lk-AD for ged-emacs-devel@m.gmane-mx.org; Mon, 01 Jul 2024 19:41:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sOL1W-0007Ya-FX; Mon, 01 Jul 2024 13:41:06 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sOL1U-0007Y4-AR for emacs-devel@gnu.org; Mon, 01 Jul 2024 13:41:04 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sOL1N-0008Od-FC for emacs-devel@gnu.org; Mon, 01 Jul 2024 13:41:04 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 671FB240027 for ; Mon, 1 Jul 2024 19:40:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1719855654; bh=PqMRRuKWm7WA30kWqEj35/wmJFy663j2t9WsQFDsUH4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=dfgXGZOFl6zAfixJlbDQScXXRQCXVGbgtEpJ6tH3sVx0PLkChoA4vYqdzO6ymVbcs bLH0y4igPky3216MAuRAmIYCjQJx0zViegSv4srzk1GeT/wd+/6E18TI+PYQkMPh6f +A4inG2+ZDBD2i4pcM1Hb3vBdd7t69pj3yM5Si9dUa4EO6GfZziOQG7vtV3f/F4wCE fARVfcdKHUi5MDLdRaOsYp3J3hwV4Wc5e1500D+afi+58IjsF5qQBaDIEqqMBtQczd bLsmG1CXj7yaSVFLdT8y+Xue71MtI1gaJvcaqIT59YfDpuqwXl4Bo7iKdiz0xnz1sa 4t/OokD8P12HA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4WCYH95wLMz9rxK; Mon, 1 Jul 2024 19:40:53 +0200 (CEST) In-Reply-To: Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01 autolearn=unavailable autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:321042 Archived-At: Pip Cet writes: > I still think this is a simple oversight on the part of MPS, FWIW. You shouldn't allow other signals when handling SIGSEGV, or at least give the client program an option to specify a signal mask. They talk a little about why they do not block other signals. https://memory-pool-system.readthedocs.io/en/latest/design/protix.html#threads .threads.suspend: The SIGSEGV signal handler does not mask out any signals, so a thread may be suspended while the handler is active, as required by the design (see design.mps.pthreadext.req.suspend.protection). The signal handlers simply nest at top of stack. -- Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at