From: Reini U. <ru...@x-...> - 2006-08-12 12:41:29
|
bug #1538436 https://sourceforge.net/tracker/index.php?func=detail&aid=1538436&group_id=1355&atid=101355 I've added a printf at the location in question and then exhausted the stack inside the debugger. /* Only SUBRs and functions occur as bt_function. */ /* http://sourceforge.net/tracker/index.php?func=detail&aid=1538436&group_id=1355&atid=101355 */ printf("stackptr=0x%x, funcptr=0x%x\n",stack, fun); NOTREACHED; => $ ./lisp -q -M lispinit.mem -E 1:1 -B . -m 1800KW -norc -i /usr/src/clisp/bug-1538436-debug.lisp ;; Loading file /usr/src/clisp/bug-1538436-debug.lisp ... Type EXIT <enter> QUIT <enter> after the error, and continue with (set 'b '(eval a))(eval a) then *** - EVAL: variable SET has no value The following restarts are available: USE-VALUE :R1 You may input a value to be used instead of SET. STORE-VALUE :R2 You may input a new value for SET. SKIP :R3 skip SET STOP :R4 stop loading file /usr/src/clisp/bug-1538436-debug.lisp Break 1 [1]> (set 'b '(eval a))(eval a) (EVAL A) Break 1 [1]> *** - Program stack overflow. RESET Break 1 [1]> stackptr=0x7c9232f8, funcptr=0x7c91e3ed *** - Internal error: statement in file "debug.d", line 1151 has been reached!! Please send the authors of the program a description how you produced this error! Break 1 [2]> and attached gdb to our lisp: (gdb) x 0x7c9232f8 0x7c9232f8 <ntdll!CsrProbeForWrite+87>: 0x850ffb3b (gdb) x 0x7c91e3ed 0x7c91e3ed <ntdll!ZwRequestWaitReplyPort+12>: 0x90000cc2 Does this give someone a hint? -- Reini |
From: Reini U. <ru...@x-...> - 2006-08-12 12:56:39
|
Reini Urban schrieb: > stackptr=0x7c9232f8, funcptr=0x7c91e3ed > > *** - Internal error: statement in file "debug.d", line 1151 has been > reached!! > Please send the authors of the program a description how you > produced this error! > Break 1 [2]> > > and attached gdb to our lisp: > > (gdb) x 0x7c9232f8 > 0x7c9232f8 <ntdll!CsrProbeForWrite+87>: 0x850ffb3b > (gdb) x 0x7c91e3ed > 0x7c91e3ed <ntdll!ZwRequestWaitReplyPort+12>: 0x90000cc2 > > Does this give someone a hint? And apparently the --with-debug build is not affected. Cannot reproduce the broken bt there. -- Reini Urban |