From: Tim D. Jr. <ti...@te...> - 2006-11-22 00:50:02
|
Hi, I'm using the sbcl-0.9.18-ppc-darwin binary from sbcl.org and relatively recent CVS slime. I see the following when I invoke an undefined function. It's not causing me any trouble, but it seems like it's not meant to happen. Let me know if you'd like any more info. ; SLIME 2006-11-03 CL-USER> (foo) ; in: LAMBDA NIL ; (FOO) ; ; caught STYLE-WARNING: ; undefined function: FOO ; ; caught STYLE-WARNING: ; This function is undefined: ; FOO ; ; compilation unit finished ; caught 2 STYLE-WARNING conditions debugger invoked on a SB-INT:BUG: PC-OFFSET (-25215892) not in code object. Frame details:PC: #X14A60CODE: #<code object NIL {118671B7}>CODE FUN: #<FUNCTION {118671CD}>LRA: #X1000BC67COMPUTED RETURN: #X1005AE34. This is probably a bug in SBCL itself. (Alternatively, SBCL might have been corrupted by bad user code, e.g. by an undefined Lisp operation like (FMAKUNBOUND (QUOTE COMPILE)), or by stray pointers from alien code or from unsafe Lisp code; or there might be a bug in the OS or hardware that SBCL is running on.) If it seems to be a bug in SBCL itself, the maintainers would like to know about it. Bug reports are welcome on the SBCL mailing lists, which you can find at <http://sbcl.sourceforge.net/>. Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. restarts (invokable by number or by possibly-abbreviated name): 0: [CONTINUE ] Set PC-OFFSET to zero and continue backtrace. 1: [ABORT-REQUEST] Abort handling SLIME request. 2: [ABORT ] Exit debugger, returning to top level. (SB-DI::FIND-ESCAPED-FRAME #.(SB-SYS:INT-SAP #X00705B40)) 0] Cheers, Tim |
From: Christophe R. <cs...@ca...> - 2006-11-23 10:35:21
|
"Tim Daly, Jr." <ti...@te...> writes: > I'm using the sbcl-0.9.18-ppc-darwin binary from sbcl.org and > relatively recent CVS slime. I see the following when I invoke an > undefined function. It's not causing me any trouble, but it seems > like it's not meant to happen. Let me know if you'd like any more info. Can you check that it happens without slime? (Not that I really blame slime in this case, unless, I guess, you're using it in SIGIO mode). Thanks, Christophe |
From: Nikodemus S. <nik...@ra...> - 2006-11-24 10:51:43
|
"Tim Daly, Jr." <ti...@te...> writes: > Hi, > > I'm using the sbcl-0.9.18-ppc-darwin binary from sbcl.org and > relatively recent CVS slime. I see the following when I invoke an > undefined function. It's not causing me any trouble, but it seems > like it's not meant to happen. Let me know if you'd like any more info. > > ; SLIME 2006-11-03 > CL-USER> (foo) > ; in: LAMBDA NIL > ; (FOO) > ; > ; caught STYLE-WARNING: > ; undefined function: FOO > > ; > ; caught STYLE-WARNING: > ; This function is undefined: > ; FOO > ; > ; compilation unit finished > ; caught 2 STYLE-WARNING conditions > > debugger invoked on a SB-INT:BUG: PC-OFFSET (-25215892) not in > code object. Frame details:PC: #X14A60CODE: #<code object NIL > {118671B7}>CODE FUN: #<FUNCTION {118671CD}>LRA: #X1000BC67COMPUTED > RETURN: #X1005AE34. This is probably a bug in SBCL itself. > (Alternatively, SBCL might have been corrupted by bad user code, e.g. > by an undefined Lisp operation like (FMAKUNBOUND (QUOTE COMPILE)), or > by stray pointers from alien code or from unsafe Lisp code; or there > might be a bug in the OS or hardware that SBCL is running on.) If it > seems to be a bug in SBCL itself, the maintainers would like to know > about it. Bug reports are welcome on the SBCL mailing lists, which > you can find at <http://sbcl.sourceforge.net/>. > > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. > > restarts (invokable by number or by possibly-abbreviated name): > 0: [CONTINUE ] Set PC-OFFSET to zero and continue backtrace. > 1: [ABORT-REQUEST] Abort handling SLIME request. > 2: [ABORT ] Exit debugger, returning to top level. > > (SB-DI::FIND-ESCAPED-FRAME #.(SB-SYS:INT-SAP #X00705B40)) > 0] "Happily" I can reproduce this. I thought I could not, but turns out I was running Slime from the wrong tree... Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |
From: Nikodemus S. <nik...@ra...> - 2006-11-24 10:57:46
|
Nikodemus Siivola <nik...@ra...> writes: >> debugger invoked on a SB-INT:BUG: PC-OFFSET (-25215892) not in >> code object. Frame details:PC: #X14A60CODE: #<code object NIL >> {118671B7}>CODE FUN: #<FUNCTION {118671CD}>LRA: #X1000BC67COMPUTED >> RETURN: #X1005AE34. This is probably a bug in SBCL itself. >> (Alternatively, SBCL might have been corrupted by bad user code, e.g. >> by an undefined Lisp operation like (FMAKUNBOUND (QUOTE COMPILE)), or >> by stray pointers from alien code or from unsafe Lisp code; or there >> might be a bug in the OS or hardware that SBCL is running on.) If it >> seems to be a bug in SBCL itself, the maintainers would like to know >> about it. Bug reports are welcome on the SBCL mailing lists, which >> you can find at <http://sbcl.sourceforge.net/>. >> >> Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL. >> >> restarts (invokable by number or by possibly-abbreviated name): >> 0: [CONTINUE ] Set PC-OFFSET to zero and continue backtrace. >> 1: [ABORT-REQUEST] Abort handling SLIME request. >> 2: [ABORT ] Exit debugger, returning to top level. >> >> (SB-DI::FIND-ESCAPED-FRAME #.(SB-SYS:INT-SAP #X00705B40)) >> 0] > > "Happily" I can reproduce this. I thought I could not, but turns out > I was running Slime from the wrong tree... I'll take that back. Slime is not to blame: backtracing an undefined function on ppc/darwin does this in the REPL too. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |
From: Nikodemus S. <nik...@ra...> - 2006-11-26 13:27:54
|
"Tim Daly, Jr." <ti...@te...> writes: In backtraces from undefined functions on PPC: > debugger invoked on a SB-INT:BUG: PC-OFFSET (-25215892) not in > code object. Frame details:PC: #X14A60CODE: #<code object NIL > {118671B7}>CODE FUN: #<FUNCTION {118671CD}>LRA: #X1000BC67COMPUTED > RETURN: #X1005AE34. This is probably a bug in SBCL itself. > (Alternatively, SBCL might have been corrupted by bad user code, e.g. > by an undefined Lisp operation like (FMAKUNBOUND (QUOTE COMPILE)), or > by stray pointers from alien code or from unsafe Lisp code; or there > might be a bug in the OS or hardware that SBCL is running on.) If it > seems to be a bug in SBCL itself, the maintainers would like to know > about it. Bug reports are welcome on the SBCL mailing lists, which > you can find at <http://sbcl.sourceforge.net/>. The appended patch fixes this. Unless there are objections I'll merge this before the day is out despite the freeze, as this is a regression since 0.9.17, and only platforms touched by the fix are ones where without the patch a BUG is signalled. Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." 0.9.18.73: fix undefined function backtraces on PPC * undefined_tramp needs to set reg_CODE, and must have an object header. This was a regression as of 0.9.17.8. Current code adapted from MIPS, as I don't understand how the old magic header was supposed to work. Index: version.lisp-expr =================================================================== RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v retrieving revision 1.3102 diff -u -r1.3102 version.lisp-expr --- version.lisp-expr 24 Nov 2006 10:38:49 -0000 1.3102 +++ version.lisp-expr 26 Nov 2006 13:02:20 -0000 @@ -17,4 +17,4 @@ ;;; checkins which aren't released. (And occasionally for internal ;;; versions, especially for internal versions off the main CVS ;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".) -"0.9.18.72" +"0.9.18.73" Index: src/runtime/ppc-assem.S =================================================================== RCS file: /cvsroot/sbcl/sbcl/src/runtime/ppc-assem.S,v retrieving revision 1.10 diff -u -r1.10 ppc-assem.S --- src/runtime/ppc-assem.S 6 Oct 2006 10:54:16 -0000 1.10 +++ src/runtime/ppc-assem.S 26 Nov 2006 13:02:22 -0000 @@ -516,11 +516,24 @@ GFUNCDEF(xundefined_tramp) .globl CSYMBOL(undefined_tramp) -CSYMBOL(undefined_tramp): + .long SIMPLE_FUN_HEADER_WIDETAG /* header */ + .long CSYMBOL(undefined_tramp) - SIMPLE_FUN_CODE_OFFSET /* self */ + .long NIL /* next */ + .long NIL /* name */ + .long NIL /* arglist */ + .long NIL /* type */ +CSYMBOL(undefined_tramp): + /* Point reg_CODE to the header and tag it as function, since + the debugger regards a function pointer in reg_CODE which + doesn't point to a code object as undefined function. */ + bcl 20,31,.+4 /* get address of the next instruction */ + mflr reg_CODE /* header is 7 words back from here */ + addi reg_CODE,reg_CODE,-7*4+FUN_POINTER_LOWTAG + twllei reg_ZERO,trap_Cerror .byte 4 .byte UNDEFINED_FUN_ERROR - .byte 254, sc_DescriptorReg+0x40, 1 /* 140? sparc says sc_descriptorReg */ + .byte 254, sc_DescriptorReg+0x40, 1 /* 140? sparc says sc_descriptorReg */ /* This stuff is for the continuable error. I don't think there's * any support for it on the lisp side */ .align 2 |
From: Nikodemus S. <nik...@ra...> - 2006-11-26 22:18:04
|
Nikodemus Siivola <nik...@ra...> writes: > "Tim Daly, Jr." <ti...@te...> writes: > > In backtraces from undefined functions on PPC: > >> debugger invoked on a SB-INT:BUG: PC-OFFSET (-25215892) not in >> code object. Frame details:PC: #X14A60CODE: #<code object NIL >> {118671B7}>CODE FUN: #<FUNCTION {118671CD}>LRA: #X1000BC67COMPUTED >> RETURN: #X1005AE34. This is probably a bug in SBCL itself. >> (Alternatively, SBCL might have been corrupted by bad user code, e.g. >> by an undefined Lisp operation like (FMAKUNBOUND (QUOTE COMPILE)), or >> by stray pointers from alien code or from unsafe Lisp code; or there >> might be a bug in the OS or hardware that SBCL is running on.) If it >> seems to be a bug in SBCL itself, the maintainers would like to know >> about it. Bug reports are welcome on the SBCL mailing lists, which >> you can find at <http://sbcl.sourceforge.net/>. > > The appended patch fixes this. > > Unless there are objections I'll merge this before the day is out > despite the freeze, as this is a regression since 0.9.17, and only > platforms touched by the fix are ones where without the patch a BUG is > signalled. Fix committed as 0.9.18.73. Thanks for the report! Cheers, -- Nikodemus Schemer: "Buddha is small, clean, and serious." Lispnik: "Buddha is big, has hairy armpits, and laughs." |