From: Eli Zaretskii <eliz@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25990-done@debbugs.gnu.org, phillip.lord@russet.org.uk
Subject: bug#25990: 25.1; emacs_backtrace.txt
Date: Tue, 07 Mar 2017 17:40:38 +0200 [thread overview]
Message-ID: <83zigxgknd.fsf@gnu.org> (raw)
In-Reply-To: <83o9xfhy4q.fsf@gnu.org> (message from Eli Zaretskii on Mon, 06 Mar 2017 05:39:33 +0200)
> Date: Mon, 06 Mar 2017 05:39:33 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 25990@debbugs.gnu.org
>
> > Date: Sun, 5 Mar 2017 16:53:02 -0800 (PST)
> > From: Drew Adams <drew.adams@oracle.com>
> >
> > Dunno whether this backtrace from an emacs -Q session helps:
> >
> > Backtrace:
> > 0000000400174f80
> > 000000040017501a
> > 00000004000a629a
> > 00000004000be496
> > 00000004000bf1c4
> > 00000004001c5628
> > 0000000076d07950
> > 0000000076d18125
> > 0000000076d08557
> > 0000000076d3bcb0
> > 000007fefe575227
> >
> >
> > In GNU Emacs 25.1.1 (x86_64-w64-mingw32)
> > of 2016-11-15 built on LAPHROAIG
>
> Phillip, can you convert this to file names and line numbers, please?
Never mind, I did it myself:
w32_backtrace at C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/w32fns.c:9804
emacs_abort at C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/w32fns.c:9836
terminate_due_to_signal at C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/emacs.c:376
handle_fatal_signal at C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/sysdep.c:1601
deliver_thread_signal at C:\msys64\home\user\emacs-git\build\x86_64\emacs-25.1-2\src/../../../../git/emacs-25.1/src/sysdep.c:1559
_gnu_exception_handler at C:/repo/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/crt_handler.c:220
This means that the information about the actual locus of the crash is
lost, and there's nothing that can be done about this report. So I'm
closing it.
Once again, if Drew wants these crashes to be investigated and solved,
he will find a way to run Emacs under GDB and report more useful
information about crashes.
next prev parent reply other threads:[~2017-03-07 15:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 0:53 bug#25990: 25.1; emacs_backtrace.txt Drew Adams
2017-03-06 3:39 ` Eli Zaretskii
2017-03-07 15:40 ` Eli Zaretskii [this message]
2017-03-06 4:08 ` npostavs
2017-03-06 4:49 ` Drew Adams
2017-03-06 14:06 ` Noam Postavsky
2017-03-06 15:03 ` Drew Adams
2017-03-06 16:06 ` Eli Zaretskii
[not found] <<90a01398-49ae-4d1d-8977-c2eb50414c38@default>
[not found] ` <<8760jn9hd2.fsf@users.sourceforge.net>
[not found] ` <<83mvcyie53.fsf@gnu.org>
2017-03-06 16:11 ` Drew Adams
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=83zigxgknd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25990-done@debbugs.gnu.org \
--cc=phillip.lord@russet.org.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 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).