bug#899: marked as done (23.0.60; Opening a foo.tar.gz file crashes)

[owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)]

[-- Attachment #1: Type: text/plain, Size: 855 bytes --]


Your message dated Wed, 24 Dec 2008 19:20:30 +0800
with message-id <49521AFE.4030105@gnu.org>
and subject line Re: bug#716: Bug in buffer-swap-text
has caused the Emacs bug report #716,
regarding 23.0.60; Opening a foo.tar.gz file crashes
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
716: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=716
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems

[-- Attachment #2: Type: message/rfc822, Size: 4211 bytes --]

From: Yary Hluchan <yary@apicom.com>
To: emacs-pretest-bug@gnu.org
Subject: 23.0.60; Opening a foo.tar.gz file crashes
Date: Fri, 05 Sep 2008 16:11:12 -0700
Message-ID: <200809052311.m85NBCQk004744@bell.apicom.com>


Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.

Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.

Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:

Create a couple small text files- in my case sample1.txt containing:
Here is a sample. Hello!
and sample2.txt containing:
foo bar bat baz

put them in an archive with:
tar -czf sample.tar.gz sample?.txt

Then open a fresh instance of emacs, C-x C-f sample.tar.gz and it crashes.

I don't have gdb installed, but I can give you a link to sample.tar.gz
http://www.driveway.com/r4h5t5i7r1
My other tar.gz archives also crash emacs.

If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
    `bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/Program Files/Emacs/Unpatched/emacs/etc/DEBUG for instructions.


In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-09-03 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include -fno-crossjumping'

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: ENU
  value of $XMODIFIERS: nil
  locale-coding-system: cp1252
  default-enable-multibyte-characters: t

Major mode: Fundamental

Minor modes in effect:
  recentf-mode: t
  partial-completion-mode: t
  tooltip-mode: t
  mouse-wheel-mode: t
  menu-bar-mode: t
  file-name-shadow-mode: t
  global-font-lock-mode: t
  blink-cursor-mode: t
  global-auto-composition-mode: t
  auto-encryption-mode: t
  auto-compression-mode: t
  line-number-mode: t
  transient-mark-mode: t

Recent input:
<escape> x r e p o <tab> r <tab> <return>

Recent messages:

An error has occurred while loading `c:/Documents and Settings/Stephen Edwards/Application Data/.emacs':

File error: Cannot open load file, menuacc

To ensure normal operation, you should investigate and remove the
cause of the error in your initialization file.  Start Emacs with
the `--debug-init' option to view a complete error backtrace.

For information about GNU Emacs and the GNU system, type C-h C-a.



[-- Attachment #3: Type: message/rfc822, Size: 3182 bytes --]

From: Jason Rumney <jasonr@gnu.org>
To: 716-done@emacsbugs.donarmstrong.com
Subject: Re: bug#716: Bug in buffer-swap-text
Date: Wed, 24 Dec 2008 19:20:30 +0800
Message-ID: <49521AFE.4030105@gnu.org>

Stefan Monnier wrote:
> Thanks.  After your email, I thought we could just change
> r_alloc_reset_variable to take 2 arguments: the old ptr and the
> new ptr.  This way, you get more consistency checking.
>   

I've checked in a change that does this.