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
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
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 cutpaste made a mess
Dear Jörg,
* Jörg F. Wittenberger joerg.wittenber...@softeyes.net [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