From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#53136: 28.0.90; segfault in lock_file Date: Sun, 09 Jan 2022 17:40:17 +0800 Message-ID: <87mtk5tfge.fsf@yahoo.com> References: <871r1hv40o.fsf.ref@yahoo.com> <871r1hv40o.fsf@yahoo.com> <83bl0l2we3.fsf@gnu.org> <87r19htjlp.fsf@yahoo.com> <838rvp2tcw.fsf@gnu.org> Reply-To: Po Lu Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2580"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.60 (gnu/linux) Cc: 53136@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jan 09 10:49:00 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1n6Uot-0000Rf-QX for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 09 Jan 2022 10:48:59 +0100 Original-Received: from localhost ([::1]:35908 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n6Uos-0007W1-RN for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 09 Jan 2022 04:48:58 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:56038) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n6UhC-0004Ml-9Z for bug-gnu-emacs@gnu.org; Sun, 09 Jan 2022 04:41:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:56321) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n6UhC-0008F4-0C for bug-gnu-emacs@gnu.org; Sun, 09 Jan 2022 04:41:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n6UhB-0007nm-Qg for bug-gnu-emacs@gnu.org; Sun, 09 Jan 2022 04:41:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Po Lu Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 09 Jan 2022 09:41:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53136 X-GNU-PR-Package: emacs Original-Received: via spool by 53136-submit@debbugs.gnu.org id=B53136.164172123729951 (code B ref 53136); Sun, 09 Jan 2022 09:41:01 +0000 Original-Received: (at 53136) by debbugs.gnu.org; 9 Jan 2022 09:40:37 +0000 Original-Received: from localhost ([127.0.0.1]:49224 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n6Ugn-0007n1-0P for submit@debbugs.gnu.org; Sun, 09 Jan 2022 04:40:37 -0500 Original-Received: from sonic313-56.consmr.mail.ne1.yahoo.com ([66.163.185.31]:36807) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n6Ugk-0007mn-WE for 53136@debbugs.gnu.org; Sun, 09 Jan 2022 04:40:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1641721229; bh=RaHhvPt6dXBbirJalvtHhWV/r0Vv3Y+6JpGC4fBVSJQ=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From:Subject:Reply-To; b=eJJTcpibKBORZT8ja7jGO5SFXaRefCNpuvQm4aZcPZeDxOlRr9/ihGvEj3y2pRGTgnml6GMYp7B1BNCMZ5KX/5i9UR7MiB6MfWmS6mJf9yNnRd5Bv/7wjK+HnLMNRn9yZmPdmw01QuR+rjRoyKgpMU3CyE3NEVmOgb0R1rSNzhw7pfuZcAZPKtlrRDlmyRx7oNKFt1U/oN+8JO3hu4C62ZwP8rkIdZcJ7/CELSnuf02UvpoUTdKfdY5zOanUYRRcXYmnQUO/MOz/OxR1CntuJAxZYMddbiOiUjnJQIMXm7h/NhYCHJJ5+IkceE/kB/gh6j+cpocalCyVN2qw/jMl/w== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1641721229; bh=r1M+9N2B8pSO9e15fIcC87XK5CGJAKJpiw4onJu1F7+=; h=X-Sonic-MF:From:To:Subject:Date:From:Subject; b=FrVrZLpt8HwiDkbydQLVBahdhxqezs9Tly+o5LMGOFd6ZEsq2W+mZ1esFzd8GUcG/MnB4fYGxxd6QMzku2cVUZAC0PXHqQ7N8bhPVnpkiQivoMJP/q7JkLKKl/COcX3AowWINgkk8wZtEwfugx+wWqJGWabmLRxdG6ZDbont/kD4yfr7Pw9XJZac0bxRzagtyVlgLEhopQdX3noa6YPgCgYpdYhPybcOBRb/2/EFaYKMbK/BNaKZXzcZL6ifYg00npF4jrL3W3zL/fkGkd0602pmEMk/lCMU1voT2cU0bFu7n/KwjsKb//za86rUQSLPddZ3+Z22YbdikOaxJkQ7eg== X-YMail-OSG: 1CDJM2sVM1k8M6RbsVBoLIQKvdAg54S4a5Tky._RCniCCMAQzx0yY9ZOav.0Zi1 XdIFJFGBs162.BnpYAojv9Hu5TYQeE4HHBGwqFsJO2kdKgK2OvpwLJL2kp5Qi2kPTt6ogkpkj9al yS7oiDUcs71LIXLlM_qwSrotBzxIuo6nQyAP13hOJhq7gCkqNOWgB2JZV_L3bShJGRwjsxckDqdw BDinl1z24BPxcW18L68bFq3vxlvp6VrP7_D2kGc187JYn7nfATrzTK82xQaLFbUDTy70FoRumded G6_X_.CaKz0CDXyS1kwCK2JMwXmqEwlMpyeYncAAvEG8eOHC5XaqpH.yxhZtuW2X3rcKUr_Aacyb TXF_3J4hiGMDRmBKc_wAsCMhTcSS2xGjJkkut9K4EBchhXCCjCTqC2J7ywo8zhn9gCmJrCJMyRJj ikIKwA3HmJQ8886sxvqJ85xJ37vTnjuzqGWANE3BUb5ozEvtNVAXRuS2owg9wiwb8nWVrc0G73Gi vAORP2TQm1uy2tuMBBimQr.upCRk2LR5qG9RC8NsviOAcLYVuenH970JlAD47fzU3um4y2IRRBfK 8qqryB9fEk8gmrYZTRO6WKc3qwakY7SATXqDBSHtXw57b.oniHg6NChE.qK36qmLCKSjP98.OJKe .5n7vHdin4zrzj0W4VeiSbofcyJSk1TNS38afy.pVkBvKCINlhn82jZNRevFI0dBIuVtl.t7FBJ3 b0DTpViunJ4yRHwHjoVbLCeFbFqKYa6UggZ.btgrUl7iJT5N9Yxk5s2fAjYRJt_DtiwydLWAdHkK 6TeEDRzujE8u_5_.OINw2vHCGUUUzxuBNmrU8xkSuK X-Sonic-MF: Original-Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.ne1.yahoo.com with HTTP; Sun, 9 Jan 2022 09:40:29 +0000 Original-Received: by kubenode517.mail-prod1.omega.sg3.yahoo.com (VZM Hermes SMTP Server) with ESMTPA ID c8c8c78a184a1a13637ea158bb3a5808; Sun, 09 Jan 2022 09:40:22 +0000 (UTC) In-Reply-To: <838rvp2tcw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Jan 2022 10:42:07 +0200") X-Mailer: WebService/1.1.19551 mail.backend.jedi.jws.acl:role.jedi.acl.token.atz.jws.hermes.yahoo X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:223836 Archived-At: Eli Zaretskii writes: >> gdb says dot is "optimized out" (but valgrind, which I happened to be >> running that Emacs under in an attempt to catch the GC bug I reported a >> month ago, disagrees). pidlen is 6. >> >> I will try to get more information from the valgrind core file. A superficial examination didn't reveal any string that made sense in the (stack) frame of lock_file. I will dig deeper later. > So we somehow wrote more than 8192 bytes by that memcpy line? I find > this hard to believe. Same here, I couldn't find how that happened. > What exactly did valgrind say? It complained about an invalid write of size 1 at one byte outside the current stack frame. Thanks.