vasilito
f31522130f
Build system (5 gaps hardened): - COOKBOOK_OFFLINE defaults to true (fork-mode) - normalize_patch handles diff -ruN format - New 'repo validate-patches' command (25/25 relibc patches) - 14 patched Qt/Wayland/display recipes added to protected list - relibc archive regenerated with current patch chain Boot fixes (fixable): - Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset) - D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped) - redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped) - daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch) - udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async) - relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs - greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait) - greeter-ui: built and linked (header guard unification, sem_compat stubs removed) - mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps - greeter config: removed stale keymapd dependency from display/greeter services - prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified Unfixable (diagnosed, upstream): - i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort - kded6/greeter-ui: page fault 0x8 — Qt library null deref - Thread panics fd != -1 — Rust std library on Redox - DHCP timeout / eth0 MAC — QEMU user-mode networking - hwrngd/thermald — no hardware RNG/thermal in VM - live preload allocation — BIOS memory fragmentation, continues on demand
25 lines
831 B
Plaintext
25 lines
831 B
Plaintext
Running D-Bus clients with Valgrind
|
|
====
|
|
|
|
When running programs using libdbus in Valgrind, some special care needs to be
|
|
taken so as to avoid incorrect detection of leaks in libdbus. To avoid these
|
|
false positives, do the following:
|
|
|
|
* Grab a copy of the D-Bus source code
|
|
|
|
* Run configure with the --enable-developer and --with-valgrind options
|
|
|
|
* Run make
|
|
|
|
* Either make sure your code calls dbus_shutdown() (at least while running in
|
|
Valgrind) or set DBUS_MESSAGE_CACHE=0 in your environment
|
|
|
|
* Run Valgrind on your program with the /path/to/dbus/source/dbus/.libs in your
|
|
LD_LIBRARY_PATH
|
|
|
|
Your Valgrind log should now be free of any (spurious) libdbus-related leaks.
|
|
|
|
For the curious, the DBUS_MESSAGE_CACHE=0 is required because by
|
|
default, libdbus uses a recyclable pool of message structs. These help
|
|
performance a bit.
|