From unknown Sat Aug 16 16:08:13 2025 X-Loop: don@donarmstrong.com Subject: bug#805: Emacs crashes on Windows when visiting .tar.gz files Reply-To: Glenn Morris , 805-quiet@debbugs.gnu.org Resent-From: Glenn Morris Resent-To: Resent-Date: Wed, 27 Aug 2008 20:45:05 +0000 Resent-Message-ID: Resent-Sender: don@donarmstrong.com X-Emacs-PR-Message: report 805 X-Emacs-PR-Package: emacs,w32 X-Emacs-PR-Keywords: Received: via spool by quiet@emacsbugs.donarmstrong.com id=Q.121986936816388 (code Q ref -1); Wed, 27 Aug 2008 20:45:05 +0000 X-Spam-Checker-Version: SpamAssassin 3.2.3-bugs.debian.org_2005_01_02 (2007-08-08) on rzlab.ucr.edu X-Spam-Level: X-Spam-Status: No, score=-13.4 required=4.0 tests=AWL,BAYES_00,HAS_PACKAGE, RCVD_IN_DNSWL_MED,X_DEBBUGS_NO_ACK autolearn=ham version=3.2.3-bugs.debian.org_2005_01_02 Received: (at quiet) by emacsbugs.donarmstrong.com; 27 Aug 2008 20:36:08 +0000 Received: from fencepost.gnu.org (fencepost.gnu.org [140.186.70.10]) by rzlab.ucr.edu (8.13.8/8.13.8/Debian-3) with ESMTP id m7RKa5sK016382 for ; Wed, 27 Aug 2008 13:36:06 -0700 Received: from rgm by fencepost.gnu.org with local (Exim 4.67) (envelope-from ) id 1KYRit-0008QX-F6; Wed, 27 Aug 2008 16:34:35 -0400 From: Glenn Morris To: quiet X-Spook: EuroFed subversive Semtex colonel Islam Abduganievich X-Ran: wP)!h4s\hS5r1|REQmiI*|S$cLZvgb_e|kC:qJr`$OLJ=O5/iy1YLHPv73mvj([31RBD// X-Hue: cyan X-Attribution: GM Date: Wed, 27 Aug 2008 16:34:35 -0400 Message-ID: User-Agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Package: emacs,w32 (Filing a report for old item from FOR-RELEASE.) http://lists.gnu.org/archive/html/emacs-devel/2008-06/msg01850.html Initial report: Steps to reproduce: 1. Create a small tar file with 2 or 3 files in it 2. emacs -q 3. M-x load-library tar-mode 4. Open the tar file You see the crash (with earlier posted stack trace) I saw another crash with the following steps: 1. Repeat #1, #2 from the previous scenario 2. Open the tar file, you will see the file listing 3. Position the cursor on one of the listed files and hit enter (open the file in the archive) You see a crash. Stack trace follows for 2nd scenario: