Skip to content

[FEA]: Debugger pretty-printers: cuda::std::complex/cuda::complex #10090

Description

@Jacobfaib

Create a lldb and gdb pretty printer for cuda::std::complex/cuda::complex.

The printer should live under libcudacxx/share/libcudacxx/<debugger>/complex.py for each debugger.

In addition, the pretty printers should be exhaustively tested, with tests living under libcudacxx/test/debugging/complex. See the existing tests in that directory for inspiration.

Activity

  1. HenrikGharagyozyan commented on Jul 30, 2026

    @HenrikGharagyozyan
    Contributor

    Hi! I'd like to work on this one. My plan is to follow the cuda::std::array printer pattern from #10528: add complex.py under libcudacxx/share/libcudacxx/gdb/ and libcudacxx/share/libcudacxx/lldb/, covering both cuda::std::complex and cuda::complex (both store __re_/__im_, so one matcher can handle the two class templates), plus exhaustive tests under libcudacxx/test/debugging/complex/ using the existing harness.

    Note: I'll validate the gdb printer locally but don't have lldb available in my environment, so the lldb printer will mirror the gdb logic structurally and rely on CI for verification — flagging that upfront in case it needs extra review attention.

  2. moved this from Todo to In Progress in CCCLon Jul 30, 2026
  3. moved this from In Progress to In Review in CCCLon Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomers.help wantedRequest for input or help from the communitylibcu++For all items related to libcu++

    Projects

    • Status
      In Review

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions