From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Newsgroups: gmane.emacs.bugs Subject: bug#66744: 30.0.50; Emacs crashes when re-dumping into the same dump file another Emacs instance is using Date: Thu, 26 Oct 2023 17:45:49 +0200 Message-ID: References: <87o7gnnhqz.fsf@localhost> <87a5s5bg83.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8304"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 66744@debbugs.gnu.org To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Oct 26 17:47:12 2023 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 1qw2Zk-0001yH-Nj for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 26 Oct 2023 17:47:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qw2ZS-0003QE-NK; Thu, 26 Oct 2023 11:46:54 -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 1qw2Z9-0003LB-72 for bug-gnu-emacs@gnu.org; Thu, 26 Oct 2023 11:46:41 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qw2Z5-00079A-PA for bug-gnu-emacs@gnu.org; Thu, 26 Oct 2023 11:46:33 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qw2Za-0003V0-7x for bug-gnu-emacs@gnu.org; Thu, 26 Oct 2023 11:47:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 26 Oct 2023 15:47:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66744 X-GNU-PR-Package: emacs Original-Received: via spool by 66744-submit@debbugs.gnu.org id=B66744.169833519413407 (code B ref 66744); Thu, 26 Oct 2023 15:47:02 +0000 Original-Received: (at 66744) by debbugs.gnu.org; 26 Oct 2023 15:46:34 +0000 Original-Received: from localhost ([127.0.0.1]:34357 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qw2Z7-0003UA-Ps for submit@debbugs.gnu.org; Thu, 26 Oct 2023 11:46:34 -0400 Original-Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]:53277) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qw2Z3-0003Tj-10 for 66744@debbugs.gnu.org; Thu, 26 Oct 2023 11:46:32 -0400 Original-Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-540105dea92so1593374a12.2 for <66744@debbugs.gnu.org>; Thu, 26 Oct 2023 08:45:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698335151; x=1698939951; darn=debbugs.gnu.org; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=k1Pcw+xGXLX9iXZPnUdr+xXRKs95MIQcYvEiq6BX+Ig=; b=OQ2UZd0/gt5X6Xf3XmdYBEbt5ZxfXH7lBi4nwuvi7Nb5PJLhreIA4kDIUf4TWlviZ3 TdARun/XMTzBatGBLREgEBARd3+lPtqztU4RAvYwpGYM85e5su/l2/hclsgJNyt9OqZ/ GIEv1XeYxbPz02uSxNI+pkqvQw7WwFofIiqn524hME14baBPzo2/wGiiWUF9Gt2SYPX4 W/P3WsBSZ5ZAqiFy+3UYGA2hx6PgJaVJcA4uryUOkqcdyMDqwXd9tgXWyOcTVvHsiOsc qBs6GAnk5R0Hu+7ChrI2Pj7APge9kMtbOOYsWgwwCLxNFyivIdepVjhYwH706HDOjgwH z/eg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698335151; x=1698939951; h=content-transfer-encoding:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=k1Pcw+xGXLX9iXZPnUdr+xXRKs95MIQcYvEiq6BX+Ig=; b=gW0DnAGKHdarxhMGba4Zp8fuPzp98bvWprsdbnA6QXY5T2Z+dduBgfGxG4ckzq2X1T xoEBjWKxDMGguHJh9+wfdNUqFJeA3RJJzajS3r1d4M4LUvaB10VlNy7gPd93ub3VdBN/ ShQx/7t533U7wpyR6fcD4Z1WVMS/jxu7xr/P0WoCJgdnGTJRmNKBy/kzNnAuejtbB1cM AiT8WdYqBUumQm77AK/i+U2/JErx4/PkT6II2XVYCPCkGrjoS38edCbfHUAwwUsv3v2Z 3nCvGnGs2e1OAg2b7xUPs+J4VV1QW0bNo6xi0F4Wbexz48kzZ/roLJ7pb20RmPtTEebD cZTQ== X-Gm-Message-State: AOJu0YwMOLm9Co4Ve/VaGd/6GMnzLF+JsiIBlIExqA949lrDC5s1IdRU N1v/70/MXBo7N8nZDak0Vvsoi/G68Jgfpw== X-Google-Smtp-Source: AGHT+IH1jc0yKb+z2f/1PeDW44+MMmWMxQlWx8LMBuGkQF/lZEIC3QzoMXCbB5UngjfGkp/x41Xa9A== X-Received: by 2002:a50:9e69:0:b0:53f:efbc:e42b with SMTP id z96-20020a509e69000000b0053fefbce42bmr128610ede.34.1698335150809; Thu, 26 Oct 2023 08:45:50 -0700 (PDT) Original-Received: from Pro.fritz.box (p4fe3a163.dip0.t-ipconnect.de. [79.227.161.99]) by smtp.gmail.com with ESMTPSA id i18-20020a508712000000b00536ad96f867sm11665229edb.11.2023.10.26.08.45.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 26 Oct 2023 08:45:50 -0700 (PDT) In-Reply-To: <87a5s5bg83.fsf@localhost> (Ihor Radchenko's message of "Thu, 26 Oct 2023 14:39:24 +0000") 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:273300 Archived-At: Ihor Radchenko writes: > Gerd M=C3=B6llmann writes: > >>> 2. ./src/emacs -Q --dump-file=3D"/tmp/emacs-dumped.dmp" >> >> I wasn't yet able to reproduce this here, on macOS. >> >> The stack trace says it's during mouse-highlighting, so chances are it's >> not related to the dump in step 3. What happens when you leave out step >> 3, and just try some mouse-highligting in the Emacs from step 2? > > I am running Emacs from step 2 for more than 24 hours by now with normal > usage. The linux man page for mmap says, according to Google, MAP_PRIVATE ... It is unspecified whether changes made to the file after the mmap() call are visible in the mapped region. So, if the changes made to the dump file in step 3 are visible in the mmaped dump file that Emacs from step 2 uses, that would be a bit suboptimal :-). I'll leave it to the maintainers to decide if this needs action.