From: SourceForge.net <no...@so...> - 2006-02-23 18:56:22
|
Bugs item #1437616, was opened at 2006-02-23 13:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Bruno Haible (haible) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-02-28 10:04:26
|
Bugs item #1437616, was opened at 2006-02-23 19:56 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) >Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 11:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-02-28 13:42:00
|
Bugs item #1437616, was opened at 2006-02-23 13:56 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2006-02-28 08:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 05:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-03-13 10:55:41
|
Bugs item #1437616, was opened at 2006-02-23 19:56 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-03-13 11:55 Message: Logged In: YES user_id=377168 >STACK depth: 16359 This is unusually low. Note that this report is wrong by a factor of 4 (fixed locally, not yet in CVS). What is your -m setting? What does ulimit -s report? What does sigsegv.h #define (or not) about SIGSEGV? On my Linux box, the STACK depth report (prior to fix) is either ~111000 or ~450000, depending on build options. The corresponding -m default is either 2MB or 14MB. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-02-28 14:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 11:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-03-13 14:33:51
|
Bugs item #1437616, was opened at 2006-02-23 13:56 Message generated for change (Comment added) made by sds You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Sam Steingold (sds) Date: 2006-03-13 09:33 Message: Logged In: YES user_id=5735 >>STACK depth: 16359 >This is unusually low. this may be an artifact of -with-debug (object_struct?) I do not pas -m $ ulimit -s 10240 sigsegv.h is attached. I think the limits should not be relevant: they affect the arguments that trigger the bug, not the bug itself. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-13 05:55 Message: Logged In: YES user_id=377168 >STACK depth: 16359 This is unusually low. Note that this report is wrong by a factor of 4 (fixed locally, not yet in CVS). What is your -m setting? What does ulimit -s report? What does sigsegv.h #define (or not) about SIGSEGV? On my Linux box, the STACK depth report (prior to fix) is either ~111000 or ~450000, depending on build options. The corresponding -m default is either 2MB or 14MB. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-02-28 08:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 05:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-03-29 15:54:06
|
Bugs item #1437616, was opened at 2006-02-23 19:56 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-03-29 17:54 Message: Logged In: YES user_id=377168 Your attached sigsegv file shows /* HAVE_STACK_OVERFLOW_RECOVERY is defined if stack overflow can be caught. */ #if 0 # define HAVE_STACK_OVERFLOW_RECOVERY 1 Program stack overflow will crash CLISP. Possibly, libsigsegv is badly configured on your system (see the libsigsegv bug page on sourceforge), if it uses gcc4, as was the case on my Ubuntu/Debian breezy box: the kernel provides for stack overflow recovery, yet libsigsegv's configure did not recognize that. Please try combinations of ulimit -s (and clisp -m) to play with various C (and LISP stack) sizes to ensure that it's not an uncaught program stack overflow that you're running into. Lazy streams *do* pile up on the stack. Please try to find out why STACK depth is so low (-m option). Note that a fixed libsigsegv will only help with program stack overflows. CLISP should be able to detect a LISP stack overflow on its own (well, should it? pushSTACK does not check bounds, they are checked here and then). Possibly this is a red herring and the problem lies with g++ --with-debug... ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-03-13 15:33 Message: Logged In: YES user_id=5735 >>STACK depth: 16359 >This is unusually low. this may be an artifact of -with-debug (object_struct?) I do not pas -m $ ulimit -s 10240 sigsegv.h is attached. I think the limits should not be relevant: they affect the arguments that trigger the bug, not the bug itself. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-13 11:55 Message: Logged In: YES user_id=377168 >STACK depth: 16359 This is unusually low. Note that this report is wrong by a factor of 4 (fixed locally, not yet in CVS). What is your -m setting? What does ulimit -s report? What does sigsegv.h #define (or not) about SIGSEGV? On my Linux box, the STACK depth report (prior to fix) is either ~111000 or ~450000, depending on build options. The corresponding -m default is either 2MB or 14MB. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-02-28 14:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 11:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-03-30 16:57:07
|
Bugs item #1437616, was opened at 2006-02-23 19:56 Message generated for change (Comment added) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault Status: Open Resolution: None Priority: 5 Submitted By: Sam Steingold (sds) Assigned to: Nobody/Anonymous (nobody) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- >Comment By: Jörg Höhle (hoehle) Date: 2006-03-30 18:57 Message: Logged In: YES user_id=377168 On my Ubuntu box, a -DWIDE nodebug build with bad libsigsegv gets a sigsegv with ulimit -s 3500, and succeeds with ulimit -s4000. g++ and -with-debug could make such a difference that much more program stack is used so that you get a sigsegv despite ulimit -s10240 -- really ?!? Joerg ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-29 17:54 Message: Logged In: YES user_id=377168 Your attached sigsegv file shows /* HAVE_STACK_OVERFLOW_RECOVERY is defined if stack overflow can be caught. */ #if 0 # define HAVE_STACK_OVERFLOW_RECOVERY 1 Program stack overflow will crash CLISP. Possibly, libsigsegv is badly configured on your system (see the libsigsegv bug page on sourceforge), if it uses gcc4, as was the case on my Ubuntu/Debian breezy box: the kernel provides for stack overflow recovery, yet libsigsegv's configure did not recognize that. Please try combinations of ulimit -s (and clisp -m) to play with various C (and LISP stack) sizes to ensure that it's not an uncaught program stack overflow that you're running into. Lazy streams *do* pile up on the stack. Please try to find out why STACK depth is so low (-m option). Note that a fixed libsigsegv will only help with program stack overflows. CLISP should be able to detect a LISP stack overflow on its own (well, should it? pushSTACK does not check bounds, they are checked here and then). Possibly this is a red herring and the problem lies with g++ --with-debug... ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-03-13 15:33 Message: Logged In: YES user_id=5735 >>STACK depth: 16359 >This is unusually low. this may be an artifact of -with-debug (object_struct?) I do not pas -m $ ulimit -s 10240 sigsegv.h is attached. I think the limits should not be relevant: they affect the arguments that trigger the bug, not the bug itself. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-13 11:55 Message: Logged In: YES user_id=377168 >STACK depth: 16359 This is unusually low. Note that this report is wrong by a factor of 4 (fixed locally, not yet in CVS). What is your -m setting? What does ulimit -s report? What does sigsegv.h #define (or not) about SIGSEGV? On my Linux box, the STACK depth report (prior to fix) is either ~111000 or ~450000, depending on build options. The corresponding -m default is either 2MB or 14MB. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-02-28 14:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 11:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |
From: SourceForge.net <no...@so...> - 2006-04-28 08:40:10
|
Bugs item #1437616, was opened at 2006-02-23 19:56 Message generated for change (Settings changed) made by hoehle You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: clisp Group: segfault >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Sam Steingold (sds) >Assigned to: Jörg Höhle (hoehle) Summary: (nth-prime 150) segfaults Initial Comment: linux fc4 $ CC=g++ ./configure --with-debug --build build-gxx $ cd build-gxx $ gdb lisp.run (gdb) boot (gdb) run [1]> (load "benchmarks/stream.lisp") ;; Loading file benchmarks/stream.lisp ... ;; Loaded file benchmarks/stream.lisp T [2]> (nth-prime 150) Program received signal SIGSEGV, Segmentation fault. 0x0814dda4 in interpret_bytecode_ (closure=Cannot access memory at address 0xbec912d0 ) at eval.d:5896 5896 local /*maygc*/ Values interpret_bytecode_ (object closure_in, Sbvector codeptr, const uintB* byteptr_in) Warning: the current language does not match this frame. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-04-28 10:40 Message: Logged In: YES user_id=377168 thank you for your bug report. the bug has been fixed in the CVS tree. you can either wait for the next release (recommended) or check out the current CVS tree (see http://clisp.cons.org) and build CLISP from the sources (be advised that between releases the CVS tree is very unstable and may not even build on your platform). ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-30 18:57 Message: Logged In: YES user_id=377168 On my Ubuntu box, a -DWIDE nodebug build with bad libsigsegv gets a sigsegv with ulimit -s 3500, and succeeds with ulimit -s4000. g++ and -with-debug could make such a difference that much more program stack is used so that you get a sigsegv despite ulimit -s10240 -- really ?!? Joerg ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-29 17:54 Message: Logged In: YES user_id=377168 Your attached sigsegv file shows /* HAVE_STACK_OVERFLOW_RECOVERY is defined if stack overflow can be caught. */ #if 0 # define HAVE_STACK_OVERFLOW_RECOVERY 1 Program stack overflow will crash CLISP. Possibly, libsigsegv is badly configured on your system (see the libsigsegv bug page on sourceforge), if it uses gcc4, as was the case on my Ubuntu/Debian breezy box: the kernel provides for stack overflow recovery, yet libsigsegv's configure did not recognize that. Please try combinations of ulimit -s (and clisp -m) to play with various C (and LISP stack) sizes to ensure that it's not an uncaught program stack overflow that you're running into. Lazy streams *do* pile up on the stack. Please try to find out why STACK depth is so low (-m option). Note that a fixed libsigsegv will only help with program stack overflows. CLISP should be able to detect a LISP stack overflow on its own (well, should it? pushSTACK does not check bounds, they are checked here and then). Possibly this is a red herring and the problem lies with g++ --with-debug... ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-03-13 15:33 Message: Logged In: YES user_id=5735 >>STACK depth: 16359 >This is unusually low. this may be an artifact of -with-debug (object_struct?) I do not pas -m $ ulimit -s 10240 sigsegv.h is attached. I think the limits should not be relevant: they affect the arguments that trigger the bug, not the bug itself. ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-03-13 11:55 Message: Logged In: YES user_id=377168 >STACK depth: 16359 This is unusually low. Note that this report is wrong by a factor of 4 (fixed locally, not yet in CVS). What is your -m setting? What does ulimit -s report? What does sigsegv.h #define (or not) about SIGSEGV? On my Linux box, the STACK depth report (prior to fix) is either ~111000 or ~450000, depending on build options. The corresponding -m default is either 2MB or 14MB. ---------------------------------------------------------------------- Comment By: Sam Steingold (sds) Date: 2006-02-28 14:42 Message: Logged In: YES user_id=5735 STACK depth: 16359 GNU CLISP 2.35 (2005-08-29) (built 3344517961) (memory 3344522232) Software: GNU C++ 4.0.2 20051125 (Red Hat 4.0.2-8) g++ -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wno-sign-compare -Wno-invalid-offsetof -falign-functions=4 -g -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DDEBUG_GCSAFETY -DUNICODE -DDYNAMIC_FFI -I. -x none libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -lsigsegv -L/usr/X11R6/lib -lX11 SAFETY=3 HEAPCODES LINUX_NOEXEC_HEAPCODES SPVW_BLOCKS SPVW_MIXED TRIVIALMAP_MEMORY libsigsegv 2.2 Features: (READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX) C Modules: (clisp i18n syscalls regexp readline) Installation directory: /usr/local/src/clisp/current/build-g-gxx/ User language: ENGLISH Machine: I686 (I686) loiso [127.0.0.1] ---------------------------------------------------------------------- Comment By: Jörg Höhle (hoehle) Date: 2006-02-28 11:04 Message: Logged In: YES user_id=377168 Does not crash in my CVS MS-VC6 build, nor in my Ubuntu/Debian Linux gcc-4.0.2 build. What does (software-type) report? What version does fc4 ship? is libsigsegv used? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101355&aid=1437616&group_id=1355 |