unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Vincent Belaïche" <vincentb1@users.sourceforge.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Vincent Belaïche" <vincentb1@users.sourceforge.net>,
	22301@debbugs.gnu.org
Subject: bug#22301: 25.1.50; Emacs crashes while lisp debugging
Date: Wed, 20 Jan 2016 00:34:28 +0100	[thread overview]
Message-ID: <84y4blnny3.fsf@gmail.com> (raw)
In-Reply-To: <84oad2z3lp.fsf@gmail.com>

Dear Eli,

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.

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. Please note that
the `M-x report-emacs-bug' gives on the crashing Emacs the following
text:

  In GNU Emacs 25.1.50.1 (i686-pc-mingw32)
    of 2015-12-16

as was in my initial bug report.

So, where does this `i686-pc-mingw32' in the bug report come from?

   Vincent.

PS: does TRT mean "trick 'r treat" or "Turkish Radio Television"?

Le 15/01/2016 09:12, Eli Zaretskii a écrit :
>> From: Vincent Belaïche <vincentb1@users.sourceforge.net> 
>> Cc: Vincent Belaïche <vincentb1@users.sourceforge.net>  ,
>>  22301@debbugs.gnu.org
>> Date: Fri, 15 Jan 2016 08:56:44 +0100
>>
>> I had compiled with this line in the script launching it all:
>>
>>   export CPPFLAGS="$CPPFLAGS -DFOR_MSW=1 -I ${HERE_DIR}/libXpm-3.5.8/include -I ${HERE_DIR}/libXpm-3.5.8/src -L ${HERE_DIR}/libXpm-3.5.8/src"
>>
>> I will recompile with it modified as follows (-Og added):
>>
>>   export CPPFLAGS="$CPPFLAGS -Og -DFOR_MSW=1 -I ${HERE_DIR}/libXpm-3.5.8/include -I ${HERE_DIR}/libXpm-3.5.8/src -L ${HERE_DIR}/libXpm-3.5.8/src"
>>
>> Could you please confirm it is what you want before I go there.
>
> Not -Og, -O0.  Also, it's wrong to put all these into CPPFLAGS, so I
> suggest this instead (2 commands instead of one):
>
>   export CPPFLAGS="$CPPFLAGS -DFOR_MSW=1 -I ${HERE_DIR}/libXpm-3.5.8/include -I ${HERE_DIR}/libXpm-3.5.8/src"
>   export CFLAGS="$CFLAGS -O0 -g3 -L ${HERE_DIR}/libXpm-3.5.8/src"
>
>> PS: BTW, it won't be the same Emacs source code as the one crashing
>> anyway, because I did some git pull meanwhile. what shall I do with
>> that, shouldn't I try another git pull to work on the latest src
>> version, or should I try to get the same src as the one crashing by
>> getting a work area revision bashed on crashing Eamcs version
>> compilation date.
>
> Using the latest sources is always TRT.  Thanks.






  parent reply	other threads:[~2016-01-19 23:34 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 [this message]
2016-01-20  1:58   ` Alexis
2016-01-20  4:31   ` Eli Zaretskii
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

  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=84y4blnny3.fsf@gmail.com \
    --to=vincentb1@users.sourceforge.net \
    --cc=22301@debbugs.gnu.org \
    --cc=eliz@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 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).