From: Eli Zaretskii <eliz@gnu.org>
To: Michael Kleehammer <michael@kleehammer.com>
Cc: 11367@debbugs.gnu.org
Subject: bug#11367: 24.0.95.1 Crash: Windows 7 using egg
Date: Sat, 28 Apr 2012 10:13:54 +0300 [thread overview]
Message-ID: <83sjfo72h9.fsf@gnu.org> (raw)
In-Reply-To: <CAEeFzG_a3KrzbpzCyALjDn9hGvmcPA=L7M-VjZBDg1UZp6ptYw@mail.gmail.com>
> From: Michael Kleehammer <michael@kleehammer.com>
> Date: Fri, 27 Apr 2012 15:03:51 -0500
>
> I can pretty consistently crash 24.0.95.1 (and could some previous
> pre-releases).
>
> Since I am on Windows, I'm not sure how to help debug this. How can I
> generate a useful stack trace for this?
Like this:
. Download and install a MinGW build of GDB (you can find it here:
http://sourceforge.net/projects/mingw/files/MinGW/Extension/gdb/GDB-7.4/gdb-7.4-2-mingw32-bin.tar.lzma/download
. From the Emacs source repository, download the file .gdbinit,
available here:
http://bzr.savannah.gnu.org/lh/emacs/emacs-24/annotate/head:/src/.gdbinit
. Start GDB from the shell prompt in the same directory where you put
.gdbinit, like this:
gdb /path/to/emacs.exe
. When GDB starts and displays its prompt, run emacs:
(gdb) run
. Perform the steps to reproduce the problem. When Emacs crashes (or
aborts, see below), GDB will kick in, and you can type the
backtrace command:
(gdb) bt full
. Post here the backtrace. Keep the crashed session running, because
we might ask you to find out more by using additional GDB commands.
> The step that crashes is to add a new file to egg (the emacs git interface).
>
> The steps to reproduce are:
> * Create an empty repository.
> * Create file1, add, and commit with our without egg.
> * Create 2 new files.
> * Run egg-status on the directory which will show 2 untracked files.
> * Put the cursor on the first untracked file and press 's' to stage it.
Is it a crash or an abort? In the latter case, Emacs displays an
"Emacs Abort Dialog", telling that a fatal error has occurred and
asking you whether you'd like to attach a debugger.
Also, is the above reproducible from "emacs -Q"?
next prev parent reply other threads:[~2012-04-28 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 20:03 bug#11367: 24.0.95.1 Crash: Windows 7 using egg Michael Kleehammer
2012-04-28 7:13 ` Eli Zaretskii [this message]
2012-04-28 14:55 ` Michael Kleehammer
2012-04-28 15:34 ` Eli Zaretskii
2012-04-28 16:32 ` Michael Kleehammer
2012-04-28 17:22 ` Eli Zaretskii
2012-04-28 17:56 ` Michael Kleehammer
2012-04-28 18:52 ` Eli Zaretskii
2012-04-28 19:17 ` Michael Kleehammer
2012-04-28 19:24 ` Eli Zaretskii
2012-04-28 19:27 ` Michael Kleehammer
2012-04-28 20:44 ` Eli Zaretskii
2012-04-29 17:30 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sjfo72h9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11367@debbugs.gnu.org \
--cc=michael@kleehammer.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).