Attach debugger to process to debug DLL compiled from Rust code

[Ybalrid]

Hello,

I am attempting to setup CodeLLDB on Windows in a way where I could breakpoint inside a DLL that was compiled from Rust code (crate configured with cdylib, exporting a pub extern no_mangle function) that has been loaded and called inside another program (let's say, via LoadLibraryA, GetProcAddress).

I currently have this lauch.json configuration to attach to a running process:

{
    "type": "lldb",
    "request": "attach",
    "name": "CodeLLDB Attach",
    "pid": "${command:pickMyProcess}",
    "sourceLanguages": ["rust", "cpp"]
}

When doing so, the UI seems to indicate that the DLL has symbols loaded, but no breakpoints in the rust code get resolved

I do not want to debug the parent program specifically (let's assume it has no symbols; I do not have access to its source code), just the DLL that was dynamically loaded at runtime.

I had partial success attempting to debug the program via Visual Studio (not Code)'s integrated Debugger. I could step through the code, but I could not inspect variables.

Within Visual Studio Code, I can replicate this by creating a launch configuration for cppvsdbg, but obviously, this launch is a debugger that is not this GitHub project, and that is configured for C++ that I do not think supports Rust in any meaningful way. It seems to understand enough about the entry point to think it is a function called MyRustDLL::get_number(), but that's about as far as it goes.

I imagine that this use case is not the most common one and may either be not very well tested or may not be supported yet. My test setup is in this repository

[Ybalrid]

Update on this: I have rebuilt the DLL as part of making a test case for posting here (linked in the first post), and it is now working as expected. I am unsure what was going on, but I am happy this is working!