From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Eli Zaretskii <eliz-mXXj517/zsQ@public.gmane.org>
Cc: 20179-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#20179: 24.4; Crash when S-TAB'ing on Org entry
Date: Mon, 23 Mar 2015 17:03:14 +0100 [thread overview]
Message-ID: <86zj73ya4d.fsf@example.com> (raw)
In-Reply-To: <mailman.2609.1427125990.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org> (Eli Zaretskii's message of "Mon, 23 Mar 2015 17:52:18 +0200")
done
Eli Zaretskii wrote:
>> From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
>> Date: Mon, 23 Mar 2015 15:17:36 +0100
>>
>> For weeks now, I experience much more crashes than before, with Emacs
>> 24.4 on Windows:
>>
>> GNU Emacs 24.4.1 (i686-pc-mingw32) of 2014-10-20 on LEG570
>>
>> I often had no time at all to report it; those crashes were
>> ignored. Now, I feel I must report one of those occurrences to you.
>>
>> Here is a (hopefully) useful backtrace:
>
> Unfortunately, no, it isn't useful. You attached the debugger too
> late, when the fatal except was already caught by the top-level
> handler in the MinGW startup code, and by that time, all traces of the
> original exception locus are lost.
>
> Please attach GDB to Emacs right after you start a new session, type
> "continue", and let Emacs run as usual. Then the fatal exception,
> when it happens, will be delivered to GDB first, and you should be
> able to produce a more useful backtrace.
OK, will try to do so.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-03-23 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 14:17 bug#20179: 24.4; Crash when S-TAB'ing on Org entry Sebastien Vauban
2015-03-23 15:52 ` Eli Zaretskii
[not found] ` <mailman.2609.1427125990.31049.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2609.1427125990.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-03-23 16:03 ` Sebastien Vauban [this message]
[not found] ` <mailman.2610.1427126649.31049.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2610.1427126649.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-03-24 11:17 ` Sebastien Vauban
2015-03-24 13:30 ` martin rudalics
[not found] ` <mailman.2673.1427203873.31049.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2673.1427203873.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-03-24 14:32 ` Sebastien Vauban
2015-03-24 17:10 ` Eli Zaretskii
[not found] ` <mailman.2691.1427217069.31049.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.2691.1427217069.31049.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-03-30 14:39 ` Sebastien Vauban
2015-03-30 14:51 ` 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=86zj73ya4d.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=20179-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
--cc=eliz-mXXj517/zsQ@public.gmane.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 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).