Re: [gnome-db] valgrind invalid read

[Vivien Malerba <vmalerba gmail com>]

On 4 March 2010 00:47, Massimo Cora' <maxcvs email it> wrote:
> Hi Vivien,
>
> while running Anjuta on valgrind we discovered a strange thing happening on
> libgda, gda-holder.c : 1044
>
> #
> ==14546== ERROR SUMMARY: 172533 errors from 188 contexts (suppressed: 201
> from 9)
> #
> ==14546== Invalid read of size 1
> #
> ==14546==    at 0x4C264C4: strcmp (mc_replace_strmem.c:412)
> #
> ==14546==    by 0x1482D9F2: real_gda_holder_set_const_value
> (gda-holder.c:1044)
> #
> ==14546==    by 0x14589148: sdb_engine_add_new_db_file
> (symbol-db-engine-core.c:763)
>
>
> The question is: can the current_val have some uninitialized value/memory
> that causes the warning?
> The type of the value is a string, so maybe there's a dangling pointer?
>

I can't see any problem with the code. However it would be much
helpfull if you could provide a standalone example which allows me to
reproduce easily the problem and fix it.

Vivien