Re: [Chicken-users] valgrind - more details

2011-10-06 Thread Jörg F . Wittenberger
On Oct 6 2011, Peter Bex wrote: Furthermore: Also I changed my mind: I'm afraid numbers in Scheme are complex enough to use a real parser to read them. I agree. There's pure Scheme code for parsing numbers syntax in trunk of the numbers egg (and the latest release has it too). It's not very

Re: [Chicken-users] valgrind - more details

2011-10-06 Thread Peter Bex
On Thu, Oct 06, 2011 at 12:47:25PM +0200, Jörg F. Wittenberger wrote: > On Oct 5 2011, Christian Kellermann wrote: > Today I re-read the R5RS, which left me wondering. Would it be > #bi101010.1 or whould it be #b#i101010.1 ? The latter. See the Lexical Syntax section, it has these productions:

Re: [Chicken-users] valgrind - more details

2011-10-06 Thread Jörg F . Wittenberger
On Oct 5 2011, Christian Kellermann wrote: Hi Christian, Dear Jörg, * Jörg F. Wittenberger [111005 22:29]: While I've been following this valgrind hint I ran into some code in C_a_i_string_to_number ... as expectable this code is kinda complicated since the problem it solves is just below the

Re: [Chicken-users] valgrind - more details

2011-10-05 Thread Christian Kellermann
Dear Jörg, * Jörg F. Wittenberger [111005 22:29]: > While I've been following this valgrind hint I ran into some > code in C_a_i_string_to_number ... as expectable this code > is kinda complicated since the problem it solves is just below > the level where one would consider to write a real parse

Re: [Chicken-users] valgrind - more details

2011-10-05 Thread Jörg F . Wittenberger
On Oct 5 2011, Jörg F. Wittenberger wrote: I found two occurrences of strlen (C_strlen that is), which would for no good reason scan the memory while the result could be computed by simple pointer arithmetic: @@ -7519,19 +7515,19 @@ errno = 0; ... Sorry. Somehow cut&paste made a mess ou

Re: [Chicken-users] valgrind - more details

2011-10-05 Thread Jörg F . Wittenberger
On Oct 5 2011, Jörg F. Wittenberger wrote: ==13112== Conditional jump or move depends on uninitialised value(s) ==13112== at 0x510393E: C_a_i_string_to_number (in While I've been following this valgrind hint I ran into some code in C_a_i_string_to_number ... as expectable this code is kinda c

[Chicken-users] valgrind - more details

2011-10-05 Thread Jörg F . Wittenberger
I managed to narrow the valgrind complaint's scope: Try as a test: valgrind --log-file=/tmp/csi.vg --track-origins=yes csi -e "(vector 'a 'b)" The result in /tmp/csi.vg looks good. However try: valgrind --log-file=/tmp/csi.vg --track-origins=yes csi -e "42" and run into an example of the pro