Lack of cuPyNumeric/Legate/Legion debugger

[Marcus-M1999]

We don't have a debugger for Legate, Legion, or cuPyNumeric. It can be hard to understand what's going on under the hood without this insight (things like understanding memory consumption, memory movement, where the data lives, debugging errors, etc.). what is the feasibility of creating this tool at some point in the future?

[lightsighter]

memory consumption, memory movement, where the data lives

These things are rendered in the profiler. Is there something missing from the profiler to help you understand them?

debugging errors, etc. what is the feasibility of creating this tool at some point in the future?

Can you say more about what you want the workflow for such a debugger to look like? In general, the whole stack works with existing debuggers like gdb and lldb. Presumably you want something beyond the capability offered by traditional debuggers, but I think we'll need more specifics before we can determine if/how to build such a tool.