all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs 24.1 / 24.2 crashes
Date: Wed, 03 Oct 2012 19:30:43 +0200	[thread overview]
Message-ID: <838vbna2f0.fsf@gnu.org> (raw)
In-Reply-To: <80ehlfc3nh.fsf@somewhere.org>

> From: "Sebastien Vauban" <wxhgmqzgwmuf@spammotel.com>
> Date: Wed, 03 Oct 2012 11:21:06 +0200
> 
> "Sebastien Vauban" wrote:
> > Recently, without apparent reasons, I've many crashes of Emacs (daily, a
> > couple of crashes).
> 
> My second one of the day...

This is not the right place to report crashes with debugger sessions.
Either post to emacs-devel@gnu.org, or report this as a bug with
"M-x report-emacs-bug RET"

> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 7064.0x139c]
> 0x7c91120f in ntdll!DbgUiConnectToDbg () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> (gdb)
> Continuing.
> [New Thread 7064.0x1e14]
> 
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 7064.0x1e14]
> 0x7c91120f in ntdll!DbgUiConnectToDbg () from /cygdrive/c/WINDOWS/system32/ntdll.dll
> (gdb) backtrace

The correct command at this point is "thread apply all backtrace".
That's because Emacs has more than one thread, and the above backtrace
is from a non-interesting thread (the one Windows launches when a
program crashes, to allow a debugger to attach).

Please post all the info you get to emacs-devel or as part of a bug
report.

Thanks, and sorry for your trouble.



  reply	other threads:[~2012-10-03 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-03  8:41 Emacs 24.1 / 24.2 crashes Sebastien Vauban
2012-10-03  8:54 ` Jambunathan K
2012-10-03  9:21 ` Sebastien Vauban
2012-10-03 17:30   ` Eli Zaretskii [this message]
     [not found] ` <mailman.10182.1349254408.855.help-gnu-emacs@gnu.org>
2012-10-04 13:24   ` Stefan Monnier

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=838vbna2f0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.