Skip to content

mpsc queue gives valgrind errors #22762

Closed
@diwic

Description

@diwic

When running the test suite for dbus-rs under valgrind, I get some errors that I don't think is my fault, because there is nothing in the backtrace indicating that would be the case.

Here's an example of that error:

Thread 1:
Conditional jump or move depends on uninitialised value(s)
    at 0x1E9030: sync::mpsc::Receiver$LT$T$GT$::recv::h14764315989133460255
    by 0x1D5D14: run_tests_console::hc794948cddbbd498cOb 
    by 0x1D2524: test_main::h01cefcc5e315671918a
    by 0x1D9CEA: test_main_static::h37e8bff01539d867Hbb
    by 0x1D0DB8: __test::main::hd07f3551eb4cd558Y2e
    by 0x240138: rust_try_inner
    by 0x240125: rust_try
    by 0x23D514: rt::lang_start::h8ce3e548818099f0bSL
    by 0x1D0F04: main
  Uninitialised value was created by a stack allocation
    at 0x1E8457: sync::mpsc::Receiver$LT$T$GT$::recv::h14764315989133460255

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions