crash on the first statement in main()
Sam Steingold
sds@gnu.org
Thu Jun 19 22:51:00 GMT 2003
I get a segfault on the first executable line in main() (confirmed in
the debugger), both when produced by cygwin:
gcc -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
-Wno-sign-compare -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW
-DSAFETY=3 -DUNICODE -DEXPORT_SYSCALLS -DDIR_KEY -DDYNAMIC_FFI
-DNO_SIGSEGV -I. -x none modules.o regexp.o regexi.o regex.o lisp.a
-lintl libcharset.a libavcall.a libcallback.a -lreadline -lncurses
-liconv -lm -o lisp.exe
...
full/lisp.exe -B . -M base/lispinit.mem -norc -q -i regexp/regexp
-x (saveinitmem "full/lispinit.mem")
Signal 11
make: *** [full] Error 1
and mingw:
gcc -mno-cygwin -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit
-Wreturn-type -falign-functions=4 -D_WIN32 -g -DDEBUG_OS_ERROR
-DDEBUG_SPVW -DSAFETY=3 -DUNICODE -DEXPORT_SYSCALLS -DDIR_KEY
-DDYNAMIC_FFI -DNO_GETTEXT -DNO_SIGSEGV -I. -x none modules.o regexp.o
regexi.o regex.o lisp.a libcharset.a libavcall.a libcallback.a -luser32
-lws2_32 -lole32 -luuid -o lisp.exe
full/lisp.exe -B . -M base/lispinit.mem -norc -q -i regexp/regexp
-x (saveinitmem "full/lispinit.mem")
<win32 crash dialog box>
the lines don't do anything special, in fact, "p <the offending line>"
executes just fine in gdb right after the crash.
comments?!
--
Sam Steingold (http://www.podval.org/~sds)
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
Modern man is the missing link between apes and human beings.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
More information about the Cygwin
mailing list