Skip to content

Lots of assertions errors when trying to debug in GDB mode #59

@morgan-dgk

Description

@morgan-dgk

Hi, this tool works great when used in run mode but when I try and debug the same program in gdb mode I get a bunch of assertion errors of the form:

Traceback (most recent call last):
  File "/usr/lib/wayland_debug/backends/gdb_plugin/plugin.py", line 70, in stop
    connection_id, message = self.message_extractor()
                             ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/wayland_debug/backends/gdb_plugin/extract.py", line 153, in sent_message
    object = wl.UnresolvedObject(object_id, None)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/wayland_debug/core/wl/object.py", line 85, in __init__
    super().__init__(obj_id)
  File "/usr/lib/wayland_debug/core/wl/object.py", line 12, in __init__
    assert obj_id > 0
           ^^^^^^^^^^
AssertionError

When I open GDB via the flag, I also see:

Function "wl_connection_destroy" not defined.
Function "wl_closure_invoke" not defined.
Function "wl_closure_dispatch" not defined.
Function "serialize_closure" not defined.

Any ideas as to what might be going on?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions