From: Jason Rumney <jasonrumney@gmail.com>
To: robert marshall <robert.marshall@tnei.co.uk>,
716@emacsbugs.donarmstrong.com
Subject: bug#716: 23.0.60; opening tgz file causes emacs crash
Date: Fri, 22 Aug 2008 20:10:44 +0800 [thread overview]
Message-ID: <48AEACC4.2000300@gnu.org> (raw)
In-Reply-To: <48A3E7C9.8050509@tnei.co.uk>
robert marshall wrote:
> If I open a tgz (tar and gzipped file) in emacs it immediately crashes
> (giving the windows emacs abort dialog)
In trying to debug this, I think I have found where it is going wrong,
but I have no idea why and how to debug the relevant bytecode. It could
be a sign of the byte compilation going wrong on Windows (line-end or
other coding problems?), or a bug in Fbytecode somewhere (which is only
affecting Windows for some reason). The stack trace when debugging
includes the following:
#8 0x010a5e65 in Finsert (nargs=2, args=0x0) at editfns.c:2224
#9 0x0115795b in Fbyte_code (bytestr=48986435, vector=49414916,
maxdepth=48)
at bytecode.c:1265
#10 0x01023232 in funcall_lambda (fun=49839780, nargs=0,
arg_vector=0x82d854)
at eval.c:3229
#11 0x01022d11 in Ffuncall (nargs=1, args=0x82d850) at eval.c:3088
In frame #11, args[0] is tar-summarize-buffer, so at that point all
appears normal.
By frame #8 things have clearly gone wrong. How did args become a NULL
pointer, yet there are 2 args?
Currently I don't have access to a GNU/Linux machine to try a copy of
tar-mode.elc compiled there. Can someone else with access to both
platforms try that? To reproduce the bug, you need to open a tar file in
Emacs (trunk) maybe a few times (the most I have had to open one before
triggering the bug is 3 times, but often it happens first time).
next prev parent reply other threads:[~2008-08-22 12:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49521AFE.4030105@gnu.org>
2008-08-14 8:07 ` bug#716: 23.0.60; opening tgz file causes emacs crash robert marshall
2008-08-22 12:10 ` Jason Rumney [this message]
2008-08-22 16:12 ` Jason Rumney
2008-09-01 12:12 ` bug#716: Bug in buffer-swap-text (was Re: bug#716: 23.0.60; opening tgz file causes emacs crash) Jason Rumney
2008-09-01 12:19 ` Jason Rumney
2008-11-21 15:14 ` Juanma Barranquero
2008-12-24 11:30 ` bug#716: marked as done (23.0.60; " Emacs bug Tracking System
2008-09-05 23:11 ` bug#899: 23.0.60; Opening a foo.tar.gz file crashes Yary Hluchan
2008-12-24 11:30 ` bug#899: marked as done (23.0.60; Opening a foo.tar.gz file crashes) Emacs bug Tracking System
2008-10-05 4:37 ` bug#1088: 23.0.60; Crash during opening a large .tar.gz file TAKAHASHI Yoshio
2008-12-24 11:30 ` bug#1088: marked as done (23.0.60; Crash during opening a large .tar.gz file) Emacs bug Tracking System
[not found] ` <as3akqfb8k.fsf@fencepost.gnu.org>
2008-12-24 11:30 ` bug#805: marked as done (Emacs crashes on Windows when visiting .tar.gz files) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48AEACC4.2000300@gnu.org \
--to=jasonrumney@gmail.com \
--cc=716@emacsbugs.donarmstrong.com \
--cc=robert.marshall@tnei.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.