Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 21 Sep 2011 20:22:55 -0400
From: "Robert Harris" <>
To: <>
Subject: RE: Crash bug on win32-cygwin-x86-any builds



I successfully compiled JtR 1.7.8 jumbo-6-RC5 with patches 001-005 in Cygwin
with win32-cygwin-x86-any and win32-cygwin-x86-sse.   (My gcc is v4.6.0)


It required no modifications.


-Robert B. Harris from VA


From: jfoug [] 
Sent: Wednesday, September 21, 2011 12:04 PM
Subject: [john-dev] Crash bug on win32-cygwin-x86-any builds


This may be 'similar' to what Alex is seeing on the Mac OSX (or may be
totally different).  This crash ONLY happens on win32-cygwin-x86-any.  All
other builds, work just fine.


I have gotten it to work.  If I build john.o without -O2, things work.
Otherwise, I get a core, with this type message:


john 3692 exception::handle: Error while dumping state (probably corrupted


There is a john.exe.stackdump, but there is nothing in there, other than
text like the line above (probably corrupted stack).



NO other builds I have show this problem.  However, if I do a full build,
then remove -O2 from the CFLAGS, then rm john.o so it rebuilds just that
file, perform the make, and the file is happy as can be.


When I run the 'broken' version under gdb (I know nothing about gdb, so this
will be a trial and error thing), it simply bails out, listing:


Program received signal SIGSEGV, Segmentation fault.

0x0045bb27 in ?? ()


So it appears GDB is not getting any form of stack frame.





Content of type "text/html" skipped

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ