Edi,
Can you reproduce this behavior on your GNU/Linux setup?
-----Original Message----- From: cl-ppcre-devel-bounces@common-lisp.net [mailto:cl-ppcre-devel-bounces@common-lisp.net] On Behalf Of Kick Damien-DKICK1 Sent: Sunday, 18 April, 2004 03:38 To: edi@agharta.de Cc: cl-ppcre-devel@common-lisp.net Subject: RE: [cl-ppcre-devel] Problems with a regexp using CL-PPCRE 0.7.4
Edi Weitz [edi@agharta.de] wrote:
I forgot two things:
- Maybe this is an error that can only be seen on Sun OS. I don't have a Sun to test so you might want to use an x86 machine as your client if possible and see if it exposes the same problem.
Okay, I just tried this on a GNU/Linux box...
(BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {48271F41}> " kick Password:" (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR)) (BASE-STRING 1)) (BREAK-CL-PPCRE::EXPECT #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> " " (FUNCTION (T T T) (VALUES (OR NULL FIXNUM) &OPTIONAL T SIMPLE-VECTOR SIMPLE-VECTOR))
Type-error in KERNEL::OBJECT-NOT-TYPE-ERROR-HANDLER: -1 is not of type (MOD 536870911)
Restarts: 0: [ABORT] Return to Top-Level.
Debug (type H for help)
("DEFUN CREATE-BMH-MATCHER" -2) Source: ; File: /home/kick/lti/cl-ppcre-0.7.4/scanner.lisp (BMH-MATCHER-AUX) 0] backtrace
0: ("DEFUN CREATE-BMH-MATCHER" -2) 1: ("DEFUN CREATE-SCANNER-AUX" " " 0 1) 2: (BREAK-CL-PPCRE::|(PCL::FAST-METHOD EXPECT (FUNCTION STREAM))| #<unused-arg> #<unused-arg> #<Closure Over Function "DEFUN CREATE-SCANNER-AUX" {482BA659}> #<Stream for descriptor 5> ...) 3: (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...) 4: (INTERACTIVE-EVAL (BREAK-CL-PPCRE::TEST-TELNET-ARGSMMGTS5--CASE-2 "localhost" :LOGIN "kick" :PASSWORD ...)) 5: (COMMON-LISP::%TOP-LEVEL) 6: (COMMON-LISP::RESTART-LISP)
0] (software-version)
"n/a" 0] (software-type)
"Linux" 0] (lisp-implementation-version)
"18d" 0] *features*
(:ASDF :CL-PPCRE :CL-PPCRE-SAFE-AND-SLOW :PCL-STRUCTURES :PORTABLE-COMMONLOOPS :PCL :PYTHON :CMU18 :CMU18D :GENCGC :CONSERVATIVE-FLOAT-TYPE :RANDOM-MT19937 :HASH-NEW :MP :I486 :X86 :LINUX :GLIBC2 :UNIX :COMMON :CMU :NEW-COMPILER :COMMON-LISP :ANSI-CL :IEEE-FLOATING-POINT) 0]
_______________________________________________ cl-ppcre-devel site list cl-ppcre-devel@common-lisp.net http://common-lisp.net/mailman/listinfo/cl-ppcre-devel
On Mon, 19 Apr 2004 13:40:29 -0500, Kick Damien-DKICK1 DKICK1@motorola.com wrote:
Can you reproduce this behavior on your GNU/Linux setup?
No. But I /think/ I've found the bug. The reason I couldn't reproduce your results seems to be that you either didn't compile CL-PPCRE or that you used a "safe core" or somesuch. Anyway, please try if you still get your bug with this version:
http://miles.agharta.de/cl-ppcre.tgz
Thanks, Edi.
cl-ppcre-devel@common-lisp.net