[Chicken-users] Syslog string protection error

[Vok Vojwo]

I think there seems to be a string protection error in the syslog egg.
The C function openlog requires a const string and relies on the fact
that the string does not change. Normally Scheme strings are moved
around by the garbage collector. This is a problem for openlog. The
result are random strings in the syslog:

Dec  8 09:59:23 t4mshpapl104 people-bridge[6170]: Starting program.
Dec  8 09:59:32 t4mshpapl104  p[6170]: Got new request.
Dec  8 10:00:33 t4mshpapl104 [6185]: Starting program.
Dec  8 10:00:36 t4mshpapl104 [6185]: Got new request.
Dec  8 10:00:36 t4mshpapl104 p�������  [6185]: Searching for:%s

I had the same problem with Gambit:
https://mercure.iro.umontreal.ca/pipermail/gambit-list/2011-November/005505.html

I solved it with strdup:
http://code.google.com/p/gs-syslog/source/browse/syslog.scm#56

Tested with:
$ chicken-status -v
4.7.0
$ chicken-status syslog
syslog .......................................................... version: 1.1

Tested on:
$ cat /etc/redhat-release
Red Hat Enterprise Linux Client release 5.5 (Tikanga)
$ uname -s -r -v -m -p -i -o
Linux 2.6.18-194.8.1.el5PAE #1 SMP Wed Jun 23 11:16:22 EDT 2010 i686
i686 i386 GNU/Linux