Re: [Chicken-users] Spiffy is crashing

2009-04-15 Thread Peter Bex
On Wed, Apr 15, 2009 at 11:10:52AM +0200, Petter Egesund wrote: With the message: Index out of range: (/search.ssp -1) This happends before I even get started. It seems it is the line: (use utf8) that makes the trouble. If I exclude this one (which I unfortunately need) it works fine.

[Chicken-users] Spiffy is crashing

2009-04-15 Thread Petter Egesund
With the message: Index out of range: (/search.ssp -1) This happends before I even get started. It seems it is the line: (use utf8) that makes the trouble. If I exclude this one (which I unfortunately need) it works fine. I use Chicken 3.4 on linux, I would like to upgrade to version 4, but I

Re: [Chicken-users] Spiffy is crashing

2009-04-15 Thread Petter Egesund
Hi, thanks for answering. It can be reproduces by these two files below. Trying to open test.ssp (any ssp-file seems to have this problem), crashes the server. I have tried to save files in both ascii and utf8 to see if this was the problem. Petter -- test.ssp --- !-- test.ssp -- html head

UTF8 crashes http-server (was Re: [Chicken-users] Spiffy is crashing)

2009-04-15 Thread peter....@xs4all.nl
On Wed, Apr 15, 2009 at 12:34:03PM +0200, Petter Egesund wrote: Hi, thanks for answering. It can be reproduces by these two files below. Trying to open test.ssp (any ssp-file seems to have this problem), crashes the server. I have tried to save files in both ascii and utf8 to see if this

Re: UTF8 crashes http-server (was Re: [Chicken-users] Spiffy is crashing)

2009-04-15 Thread peter....@xs4all.nl
On Wed, Apr 15, 2009 at 02:09:12PM +0200, peter@xs4all.nl wrote: FWIW, I traced the problem to http-server. Even the simple example on the wiki breaks when utf8 is loaded. I will look deeper into this tonight (at work right now...), but I mention this in case anyone is reading along and

Re: UTF8 crashes http-server (was Re: [Chicken-users] Spiffy is crashing)

2009-04-15 Thread peter....@xs4all.nl
On Wed, Apr 15, 2009 at 10:55:15PM +0200, peter@xs4all.nl wrote: It's the -1 that's unexpected, since it's not a valid string index, so trying to do anything with that causes it to fail big time. It should just return #f on non-matching stuff. Still not sure what exactly causes this,