From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs: Segfault Date: Thu, 02 Jun 2022 19:43:52 +0300 Message-ID: <83ilpjdnhz.fsf@gnu.org> References: <83mtevdo42.fsf@gnu.org> <25240.58922.155620.109846@retriever.mtv.corp.google.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39659"; mail-complaints-to="usenet@ciao.gmane.io" Cc: raman@google.com, emacs-devel@gnu.org To: "T.V Raman" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Jun 02 18:46:22 2022 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 1nwnxl-000A93-TM for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jun 2022 18:46:22 +0200 Original-Received: from localhost ([::1]:46110 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nwnxj-0007rO-Ru for ged-emacs-devel@m.gmane-mx.org; Thu, 02 Jun 2022 12:46:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35964) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwnvC-00062W-WF for emacs-devel@gnu.org; Thu, 02 Jun 2022 12:43:43 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35066) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwnvC-0008Vx-LT; Thu, 02 Jun 2022 12:43:42 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=cvKpVFnyGSyU/v3+Hd5rS6aNztFZOpd7ioLxhfGLPso=; b=Cq/Wr9CFJpQi bmVobZjZGp3r7FH95PTfGqeyNHKlFzDdhXn4010KIBgGuOjXt9hPpG6oufohIvYQG9isUMkbtxFqG 4YdcXCvLOLEoQw19Lof2QBHP2eV8JDtX2ZCm0JkICFCHw+456BQZBS28/Ttl4hPHnVy11h9Hf+3EB QhD7K7hFcK9/+Yaitw6sCCvxWgwrccOCajogrk52MehvVau5Wi1RDswuOoWi1Cerzmog9TKBilM09 Vii1oSLjpkGoG7f8LS/PCDxEcEiRthsclNJHeAaBDpyulPSPfx7kRSDtVaL5FprEWw7vAAFCENShA 04h4mLEsL2F8bfO2WSWkTw==; Original-Received: from [87.69.77.57] (port=1328 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nwnvC-0002ha-38; Thu, 02 Jun 2022 12:43:42 -0400 In-Reply-To: <25240.58922.155620.109846@retriever.mtv.corp.google.com> (raman@google.com) 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" Xref: news.gmane.io gmane.emacs.devel:290580 Archived-At: > From: "T.V Raman" > Date: Thu, 2 Jun 2022 09:32:42 -0700 > Cc: raman@google.com, > emacs-devel@gnu.org > > possible since updates happen behind the scene Is there some kind of update log where you could check if an update really happened? Or maybe look at the time stamp of libc.so (and if it's a symlink, of the symlink's target)?