Re: [gmime-devel] valgrind warnings from gmime

[Jeffrey Stedfast <fejj novell com>]

not sure either - do you have a small sample program that illustrates
this problem?

Jeff

On Sun, 2008-11-02 at 17:10 +0100, Paul J Stevens wrote:
> Hi Jeff,
> 
> I'm trying to understand where these come from, and is there anything I
> can do to prevent these?
> 
> ==29397== Conditional jump or move depends on uninitialised value(s)
> ==29397==    at 0x40BB7A7: (within /usr/lib/libgthread-2.0.so.0.1600.4)
> ==29397==    by 0x415BDD8: g_static_rw_lock_writer_lock (in
> /usr/lib/libglib-2.0.so.0.1600.4)
> ==29397==    by 0x40E9559: g_type_class_ref (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x40E9A42: g_type_class_ref (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x40E9A42: g_type_class_ref (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x40D002C: g_object_newv (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x40D0570: g_object_new_valist (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x40D06DF: g_object_new (in
> /usr/lib/libgobject-2.0.so.0.1600.4)
> ==29397==    by 0x4092DB7: g_mime_stream_mem_new_with_buffer (in
> /usr/lib/libgmime-2.0.so.2.2.11)
> ==29397==    by 0x8063F1B: _set_content (dbmail-message.c:721)
> 
> 
> thanks,
> 
>