Skip to content

cuda-gdb internal error when accessing LayoutTensor #68

@ShanoToni

Description

@ShanoToni

uv/pixi CLI Version

0.53.0

Mojo Version

25.6.0

GPU Information

4060 TI (8.9)

Operating System

Ubuntu 22.04.5 LTS

Related Puzzle

Puzzle 9: GPU Debugging Workflow

What happened?

Encountered following error when attempting to access LayoutTensor input in third case of problem:

cuda-gdb/14/gdb/regcache.c:746: internal-error: cooked_read_value: Assertion `regnum < m_descr->nr_cooked_registers' failed.

Error seems related to version of cuda-gdb set from running pixi setup-cuda-gdb version is reported as:

NVIDIA (R) cuda-gdb 13.0

Steps to Reproduce

  1. From problem p09
  2. Run $ pixi setup-cuda-gdb
  3. Run command $ pixi run mojo debug --cuda-gdb --break-on-launch problems/p09/p09.mojo --third-case
  4. Inside the kernel attempt to access input for example $ p input
  5. Error occurs

Relevant Log Output

(cuda-gdb) p input
cuda-gdb/14/gdb/regcache.c:746: internal-error: cooked_read_value: Assertion `regnum < m_descr->nr_cooked_registers' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x5372cb ???
0x920084 ???
0x9202a8 ???
0xac8e61 ???
0x84c004 ???
0x8832b5 ???
0x7149b8 ???
0x715324 ???
0x707ac8 ???
0x670934 ???
0x66fce7 ???
0x679cde ???
0x679db9 ???
0x6992ae ???
0x699990 ???
0x69b193 ???
0x708d94 ???
0x706f5e ???
0x927743 ???
0x6e6752 ???
0x6e5cec ???
0x827271 ???
0x827975 ???
0x563aff ???
0x90387e ???
0x6ec17e ???
0x6ed2dd ???
0x6ec9cc ???
0x964497 ???
0x6ebcdd ???
0x6ec8bd ???
0x91ae0f ???
0xac9b1c ???
0xac9ca2 ???
0x7cf3c6 ???
0x7d0d84 ???
0x43f834 ???
0x7f819ec29d8f __libc_start_call_main
        ../sysdeps/nptl/libc_start_call_main.h:58
0x7f819ec29e3f __libc_start_main_impl
        ../csu/libc-start.c:392
0x45291d ???
0xffffffffffffffff ???
---------------------
cuda-gdb/14/gdb/regcache.c:746: internal-error: cooked_read_value: Assertion `regnum < m_descr->nr_cooked_registers' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.

Additional Context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions