On Wed, Mar 03, 2004 at 12:15:02AM +0100, Martin Nilsson (saturator) @ Pike (-) developers forum wrote:
which if e.g. s->type is T_FLOAT and s->subtype is uninitialized triggers a valgrind warning, though it really is bogus.
Well... Im my case, I figured out that n->hash is the trigger, in several other places, also errors like:
==26504== Use of uninitialised value of size 4 ==26504== at 0x81B5191: sub_node (las.c:442) ==26504== by 0x81B5642: debug_free_node (las.c:711) ==26504== by 0x81BFA3E: optimize (las.c:5335) ==26504== by 0x81CCCF3: optimize_node (las.c:5363)
I upgraded valgrind to 2.1 (latest available), and still see this error... so I guess this is not valgrind's problem...
But it is strange - hash is initialized to 0 upon allocation, so it _might_ happen that it is assigned from another uninitialized variable/location (somewhere) - valgrind's tracking depth sometimes scares me...
Regards, /Al