On 15/08/2013 7:40 PM, Ken Brown wrote:
On 8/15/2013 7:14 PM, Ryan Johnson wrote:
On 15/08/2013 6:48 PM, Ryan Johnson wrote:
On 15/08/2013 6:02 PM, Ken Brown wrote:
On 8/15/2013 5:58 PM, Ken Brown wrote:
On 8/15/2013 5:24 PM, Ryan Johnson wrote:
On 15/08/2013 5:14 PM, Ken Brown wrote:
On 8/15/2013 4:55 PM, Ryan Johnson wrote:
Program received signal SIGSEGV, Segmentation fault.
___chkstk_ms () at
/usr/src/debug/gcc-4.8.1-1/libgcc/config/i386/cygwin.S:146
You're not using the latest gcc, which is 4.8.1-3. Any chance that
that's your problem?
Heh. I actually do have the latest gcc, but somehow the upgrade
didn't
pick up the debug package (which showed as not installed in
setup.exe).
I have manually upgraded it now.
OK. But doesn't the above show that the crash is occurring in
gcc, not
emacs?
BTW, how do you compile emacs from the sources given? I tried
untarring
and patching, but I get the message:
configure: error: Emacs hasn't been ported to
`x86_64-unknown-cygwin'
systems.
Check `etc/MACHINES' for recognized configuration names.
One of the patches changes configure.ac, so you have to run
autoreconf
after applying it.
Or it might be 'autoreconf -I m4'.
Something is still wrong:
$ cd /scratch
$ tar xaf /usr/src/emacs-24.3.tar.xz
$ patch -p1 </usr/src/emacs-24.3-5.cygwin.patch
patching file emacs-24.3/CYGWIN-PATCHES/emacs-X11.postinstall
patching file emacs-24.3/CYGWIN-PATCHES/emacs-X11.preremove
patching file emacs-24.3/CYGWIN-PATCHES/emacs-w32.postinstall
patching file emacs-24.3/CYGWIN-PATCHES/emacs-w32.preremove
patching file emacs-24.3/CYGWIN-PATCHES/emacs.postinstall
patching file emacs-24.3/CYGWIN-PATCHES/emacs.preremove
Ah, it seems there's a /usr/src/configure.ac.patch that happens to
belong to emacs...
... but unfortunately it seems that -fsanitize is only supported on
Linux and Darwin right now, so there's little reason to build emacs
unless you could use some particular information that a debug build
provides. Rats.
But a build without optimization would make your backtraces more useful.
I'm not sure even a perfect stack trace will be very useful if memory
corruption is the culprit, though. All it will do is give us even
clearer detail about exactly what got clobbered, but with little
additional info about what did the clobbering.
That said, I'm game if you have anything in particular you'd like more
detail on; just let me know what you'd like to see and I'll do my best
to dig it up. Meanwhile, I'll fire off the debug build.
Ryan
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
