[Chicken-users] another news from the valgrind front

2011-10-11 Thread Jörg F . Wittenberger 

Peter,

I've got one more issue fixed wrt. the fix I posted recently 
https://lists.nongnu.org/archive/html/chicken-users/2011-10/txtQD3AT30Qxp.txt


Since I'm recovering from a big mess I made out of my build envt.
Here only a description:

In C_a_i_string_to_number there is exactf declared but (as the only
one) not initialised.  Thus we have another case for valgrind to complain
when it's used.

Please change that to exactf = 0 .

(For the curious: this one turned up under valgrind again.  However
NOT when libchicken has been build using DEBUGBUILD=1 !  Too bad.)

Best regards

/Jörg



___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] another news from the valgrind front

2011-10-11 Thread Peter Bex 
On Tue, Oct 11, 2011 at 03:24:45PM +0200, Jörg F. Wittenberger wrote:
 Peter,
 
 I've got one more issue fixed wrt. the fix I posted recently 
 https://lists.nongnu.org/archive/html/chicken-users/2011-10/txtQD3AT30Qxp.txt
 
 Since I'm recovering from a big mess I made out of my build envt.
 Here only a description:
 
 In C_a_i_string_to_number there is exactf declared but (as the only
 one) not initialised.  Thus we have another case for valgrind to complain
 when it's used.

This seems like an odd bug in the generated code then, since exactf is
*always* checked before checking exactpf (like  (exactpf  exactf)),
so this should never cause a Valgrind error.

But maybe it's a bit tricky so I'll add an initializer just in case.

Cheers,
Peter
-- 
http://sjamaan.ath.cx
--
The process of preparing programs for a digital computer
 is especially attractive, not only because it can be economically
 and scientifically rewarding, but also because it can be an aesthetic
 experience much like composing poetry or music.
-- Donald Knuth

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users