X Tutup
Skip to content

[Question] GDB tracking for rustpython  #4879

@itsankitkp

Description

@itsankitkp

This not be RustPython issue per se, but I am having trouble in getting through control flow of rustpython via gdb.
In cpython (or millions other c program), I can attach debugger and flow through lexer and then to interpreter (and then finally c functions).
For example, adding breaking point to /Include/cpython/methodobject.h:46 and stepping into func->m_self I can go into corresponding c functions.
In rustpython, stepping into jumps to rustlibs back and forth and somehow execution completes without me going to actual functions.
Note that if I attach break point to some function in *.rs, it reaches there without any issue, but this is when I know where to reach. This doesn't help if I want to find out flow and where control is going and to which function in *.rs.

Any ideas on this will be apprecitated.

Note: I also tried using rust-gdb ( gdb_load_rust_pretty_printers.py didn't really help much with prettiness, for some reason) but to no avail.

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

      X Tutup