Warning

This post was published 46 days ago. The information described in this article may have changed.

Info

This post is auto-generated from RSS feed The Rust Programming Language Forum - Latest topics. Source: Issue with debugging linked C code

I'm new to rust and the ecosystem and I have a bunch of C Libraries that I would to be able to call from my new rust project. Everything runs fine and I was able to link the archive file and call the function. However if the program goes over a call to C the debugger dies essentially.

I have a baremetal cortex processor that I am programming over jtag and then just using the debugger in vscode to connect to it.

Tools:
-vscode
-rust-analyzer extension
-native debug extension
-gnu tools (for gdb)

My launch.json looks similar to this:

"version": "0.2.0",
"configurations": [
    {
        "name": "Remote debug",
        "type": "gdb",
        "request": "launch",
        "cwd": "${workspaceRoot}",
        "executable": "${workspaceRoot}/target/armv7r-none-eabi/debug/hello_world", 
        "gdbpath" : "arm-none-eabi-gdb",
        "target" : "extended-remote localhost:3000
    }
]

Is there a different debugger I should be using? Is there something I should be changing in the launch file?

Any ideas would be helpful.

2 posts - 2 participants

Read full topic

🏷️ rust_feed