After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 568957 - Valgrind warning in gtk_widget_trigger_tooltip_query
Valgrind warning in gtk_widget_trigger_tooltip_query
Status: RESOLVED DUPLICATE of bug 554686
Product: gtk+
Classification: Platform
Component: Widget: Other
2.14.x
Other Linux
: Normal minor
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2009-01-24 08:57 UTC by Josselin Mouette
Modified: 2009-01-31 04:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Test case with instructions (2.55 KB, text/x-csrc)
2009-01-24 09:00 UTC, Josselin Mouette 		Details

Description Josselin Mouette 2009-01-24 08:57:59 UTC 
[ Original bug report from Johan Walles: http://bugs.debian.org/510873 ]

Calling gtk_widget_trigger_tooltip_query() makes tooltips not show up sporadically. Also, valgrind complains about Conditional jump or move depends on uninitialised value(s) in other code.

Removing the call to gtk_widget_trigger_tooltip_query() makes the complaint go away and makes the tooltip visible again, but since I *want* to update the tooltip not calling that function doesn't really solve the problem.

Repro case with build and repro instructions coming.
Comment 1 Josselin Mouette 2009-01-24 09:00:24 UTC 
Created attachment 127155 [details]
Test case with instructions

This was reported against GTK+ 2.12, but the issue is reproducible in 2.14. Only the stack trace is a bit different:

==2067== Conditional jump or move depends on uninitialised value(s)
==2067==    at 0x501976E: child_location_foreach (gtktooltip.c:542)
==2067==    by 0x5019699: find_widget_under_pointer (gtktooltip.c:667)
==2067==    by 0x501A514: gtk_tooltip_show_tooltip (gtktooltip.c:928)
==2067==    by 0x501A608: tooltip_popup_timeout (gtktooltip.c:1041)
==2067==    by 0x54298DA: gdk_threads_dispatch (gdk.c:473)
==2067==    by 0x743426A: g_timeout_dispatch (gmain.c:3589)
==2067==    by 0x7433AAA: g_main_context_dispatch (gmain.c:2144)
==2067==    by 0x743726C: g_main_context_iterate (gmain.c:2778)
==2067==    by 0x743779C: g_main_loop_run (gmain.c:2986)
==2067==    by 0x4F52376: gtk_main (gtkmain.c:1200)
==2067==    by 0x400E23: main (truc.c:79)
Comment 2 Matthias Clasen 2009-01-31 04:35:47 UTC 

*** This bug has been marked as a duplicate of 554686 ***