https://bugs.kde.org/show_bug.cgi?id=400119
Bug ID: 400119
Summary: Library search path in Valgrind/ldd
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: helgrind
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
When I call "evolution" it executes normally. When I call "valgrind
--tool=helgrind evolution" it print things, then comes “
==28985== This conflicts with a previous write of size 8 by thread #1
==28985== Locks held: 1, at address 0x24D28670
==28985== at 0xA5BCFD4: g_signal_newv (gsignal.c:1706)
==28985== by 0xA5BD7EC: g_signal_new_valist (gsignal.c:1902)
==28985== by 0xA5BD8C8: g_signal_new (gsignal.c:1437)
==28985== by 0xF950552: clutter_device_manager_class_intern_init
(clutter-device-manager.c:178)
==28985== by 0xA5C7EC8: g_type_class_ref (gtype.c:2232)
==28985== by 0xA5C8204: g_type_class_ref (gtype.c:2939)
==28985== by 0xA5ADD97: g_object_new_valist (gobject.c:2080)
==28985== by 0xA5ADF5B: g_object_new (gobject.c:1648)
==28985== Address 0xa7ea610 is 0 bytes inside data symbol "g_signal_nodes"
==28985==
Failed to initialize gtk+: Unable to initialize the Clutter backend: no
available drivers found.
==28985==
==28985== For counts of detected and suppressed errors, rerun with: -v” and
that is the end.
Why under helgrind is printed “Failed to initialize gtk+: Unable to initialize
the Clutter backend: no available drivers found.” but under normal start not?
Can it be, that valgrind uses different algorithms to find the shared libraris,
than the OS? I might have correct and wrong libraries and the OS happens to
load the correct ones. I use the latest valgrind
--
You are receiving this mail because:
You are watching all bug changes.
