From: Eli Zaretskii <eliz@gnu.org>
To: "Vincent Belaïche" <vincentb1@users.sourceforge.net>
Cc: 22301@debbugs.gnu.org
Subject: bug#22301: 25.1.50; Emacs crashes while lisp debugging
Date: Wed, 20 Jan 2016 06:31:13 +0200 [thread overview]
Message-ID: <8360yoc1ny.fsf@gnu.org> (raw)
In-Reply-To: <84y4blnny3.fsf@gmail.com> (message from Vincent Belaïche on Wed, 20 Jan 2016 00:34:28 +0100)
> From: Vincent Belaïche <vincentb1@users.sourceforge.net>
> Cc: Vincent Belaïche <vincentb1@users.sourceforge.net> ,
> 22301@debbugs.gnu.org
> Date: Wed, 20 Jan 2016 00:34:28 +0100
>
> I have recompiled with the latest source and using the compiler options
> which you gave me, and I do not reproduce the crash (although I have
> been debugging my SES bugs at length). I have recompiled with the 32bit
> MinGW. However I am not sure whether the Emacs version that was crashing
> (that of 2015-12-16), was compiled with this MinGW or with the 64bit
> MinGW.
If -O0 doesn't reproduce the problem, then please try with -Og
instead.
> I think that it was also compiled with the 32bit, because my MSYS fstab
> file date is "12-16 08:49", and the crashing emacs.exe date is "12-16
> 10:27". So the fstab setting (currently pointing at the 32bit MinGW
> compiler) is anterior the crashing Emacs emacs.exe. However I am not
> 100% sure, I may well have launched the compilation earlier than
> changing the fstab file, but as compiling is so long, the emacs.exe date
> could however be after the fstab modification time.
>
> In a nutshell, is there any way to know whether the crashing Emacs was
> compiled with the 32bit MinGW or with another MinGW.
I'm not sure it's worth our time to try to figure that out. Let's
concentrate on reproducing the bug instead, OK?
next prev parent reply other threads:[~2016-01-20 4:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 22:43 bug#22301: 25.1.50; Emacs crashes while lisp debugging Vincent Belaïche
2016-01-04 3:41 ` Eli Zaretskii
2016-01-04 8:00 ` Vincent Belaïche
2016-01-04 15:54 ` Eli Zaretskii
2016-01-04 22:49 ` Vincent Belaïche
2016-01-05 3:34 ` Eli Zaretskii
2016-01-05 7:17 ` Vincent Belaïche
2016-01-05 16:00 ` Eli Zaretskii
2016-01-14 16:15 ` Vincent Belaïche
2016-01-14 18:20 ` Eli Zaretskii
2016-01-14 22:54 ` Vincent Belaïche
2016-01-15 7:46 ` Eli Zaretskii
2016-01-15 7:56 ` Vincent Belaïche
2016-01-15 8:12 ` Eli Zaretskii
2016-01-19 23:34 ` Vincent Belaïche
2016-01-20 1:58 ` Alexis
2016-01-20 4:31 ` Eli Zaretskii [this message]
2016-01-20 8:50 ` Vincent Belaïche
2016-01-20 9:49 ` Eli Zaretskii
2016-01-20 15:30 ` Nicolas Richard
2016-02-01 9:18 ` Vincent Belaïche
2016-02-01 17:22 ` Vincent Belaïche
2016-02-02 7:14 ` Vincent Belaïche
2016-12-07 18:55 ` Glenn Morris
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=8360yoc1ny.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22301@debbugs.gnu.org \
--cc=vincentb1@users.sourceforge.net \
/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.