From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: Ken Brown <kbrown@cornell.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: 64-bit emacs crashes a lot
Date: Fri, 16 Aug 2013 17:20:31 -0400 [thread overview]
Message-ID: <520E979F.5050903@cs.utoronto.ca> (raw)
In-Reply-To: <520E8CAF.3070601@cornell.edu>
On 16/08/2013 4:33 PM, Ken Brown wrote:
> On 8/16/2013 3:37 PM, Eli Zaretskii wrote:
>>> Date: Fri, 16 Aug 2013 13:12:17 -0400
>>> From: Ken Brown <kbrown@cornell.edu>
>>> CC: ryan.johnson@cs.utoronto.ca, emacs-devel@gnu.org
>>>
>>> I'm attaching two of them. The first was a SEGV, the second was an
>>> abort.
>>
>> Both in regex.c.
>>
>>> Lisp Backtrace:
>>>
>>> Breakpoint 1, terminate_due_to_signal (sig=6,
>>> backtrace_limit=2147483647)
>>> at emacs.c:341
>>> 341 {
>>> The program being debugged stopped while in a function called from GDB.
>>> Evaluation of the expression containing the function
>>> (backtrace_function) will be abandoned.
>>> When the function is done executing, GDB will silently stop.
>>
>> Here, GDB called backtrace_function, which triggered an assertion
>> violation. Which probably means that the array of specbindings
>> (specpdl) is corrupted.
>>
>> Is it possible that the stack of the 64-bit Cygwin binary is too
>> small? Can you try building Emacs with a larger stack?
>
> You are brilliant! I added LDFLAGS='-Wl,--stack,4194304' to the
> compilation, and the bug is gone. Thank you.
>
> Ryan, can you confirm that this fixes the problem for your real uses
> of M-x compile?
I've been using it for an hour or so with no problems. Even the
optimized build refuses to crash in 200-300 M-x compile cycles, which is
enough to satisfy me.
Thanks for all the help, I was pulling my hair out with this one...
Ryan
next prev parent reply other threads:[~2013-08-16 21:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51F3151D.7040000@cs.utoronto.ca>
[not found] ` <51F33565.1090406@cornell.edu>
[not found] ` <51F33F52.4060405@cs.utoronto.ca>
[not found] ` <51FB1D9E.5090102@cs.utoronto.ca>
[not found] ` <20130802080211.GA18054@calimero.vinschen.de>
[not found] ` <51FB9228.2020309@cornell.edu>
[not found] ` <51FBA100.90005@cs.utoronto.ca>
[not found] ` <51FD5462.5020400@cs.utoronto.ca>
[not found] ` <51FFBDFF.7040501@cornell.edu>
[not found] ` <51FFC4F2.8080909@cs.utoronto.ca>
[not found] ` <5203D89E.6030801@cornell.edu>
[not found] ` <5203DCCA.1010105@cs.utoronto.ca>
[not found] ` <5205B364.8090007@cs.utoronto.ca>
[not found] ` <52064730.50404@cornell.edu>
[not found] ` <"52065B3C.6060104@cs.utoronto <520CCA41.3000107"@cs.utoronto.ca>
[not found] ` <520D089A.1020806@cornell.edu>
[not found] ` <83ioz6op5v.fsf@gnu.org>
[not found] ` <520D4036.8010303@cs.utoronto.ca>
[not found] ` <8361v6nhdb.fsf@gnu.org>
2013-08-16 11:37 ` 64-bit emacs crashes a lot Ryan Johnson
2013-08-16 13:10 ` Eli Zaretskii
[not found] ` <520D900A.8000907@cornell.edu>
[not found] ` <520DABDC.8020304@cs.utoronto.ca>
[not found] ` <520DBFCD.4080808@cs.utoronto.ca>
[not found] ` <8338qangma.fsf@gnu.org>
2013-08-16 11:39 ` Ryan Johnson
[not found] ` <834naqnh9t.fsf@gnu.org>
2013-08-16 11:41 ` Ryan Johnson
2013-08-16 13:31 ` Eli Zaretskii
2013-08-16 14:16 ` Ryan Johnson
2013-08-16 14:49 ` Eli Zaretskii
2013-08-16 14:20 ` Ken Brown
2013-08-16 14:24 ` Ryan Johnson
2013-08-16 15:03 ` Eli Zaretskii
2013-08-16 15:45 ` Eli Zaretskii
2013-08-16 16:51 ` Ryan Johnson
[not found] ` <520E5D71.3020307@cornell.edu>
2013-08-16 17:24 ` Ryan Johnson
2013-08-16 18:55 ` Ken Brown
2013-08-16 19:37 ` Eli Zaretskii
2013-08-16 20:17 ` Eli Zaretskii
2013-08-16 20:33 ` Ken Brown
2013-08-16 21:20 ` Ryan Johnson [this message]
2013-08-17 7:01 ` Eli Zaretskii
2013-08-17 12:17 ` Ken Brown
2013-08-16 17:46 ` Ken Brown
2013-08-17 19:43 Angelo Graziosi
2013-08-17 20:16 ` Ken Brown
2013-08-17 22:23 ` Angelo Graziosi
2013-08-18 17:43 ` Ken Brown
2013-08-18 19:10 ` Angelo Graziosi
2013-08-18 19:14 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=520E979F.5050903@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
/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.