problem with VSCode debugging on Windows

[vivid ivy]

it ain't hitting the breakpoints
I'm trying to debug a DLL btw
actually I'm trying to debug a thread the DLL spawns inside the process after it gets injected into it
launch.json

{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "debug internal",
            "type": "lldb",
            "request": "attach",
            "program": "C:\\Program Files\\WindowsApps\\Microsoft.WindowsNotepad_11.2508.38.0_x64__8wekyb3d8bbwe\\Notepad.exe",
            "args": [],
            "cwd": "${workspaceRoot}",
            "initCommands": [
                "settings set target.x86-disassembly-flavor intel"
            ]
        }
    ]
}

codelldb installed
Zig extention installed

https://github.com/ziglang/zig/issues/22039

okay I found this...

[raw kelp]

I'm personally not aware of anyone who managed CodeLLDB on Windows to work reliably with Zig. I'm personally refraining to cppvsdbg, AFAIK also Visual Studio's debugger works.

[vivid ivy]

damn man thanks
could u give me ur lanch.json pls? just wanna copy paste it quickly to see if it works

[raw kelp]

https://github.com/vadim-za/zt4i-libs/blob/main/.vscode/launch.json

I'm still retaining LLDB configurations, because occasionally I do want to use LLDB, but it works usually just to a very small and limited extent

[rapid torrent]

make sure to turn on llvm

[vivid ivy]

I just tried cppvsdbg
Win64 thread should be the thread I create from the injected dll but still no breakpoints are hit
unknown source should be a clue lol

[vivid ivy]

I might need to tweak my launch.json a little bit

[raw kelp]

AFAIK it's on by default on Windows

[raw kelp]

Afraid can't help you further, don't have much experience with debugging Zig/DLLs. OTOH, aaaaaa looks like undefined value from Zig. Maybe that could be a hint, dunno.

[vivid ivy]

it's something related to shared libs I think
debugging executables works perfectly fine I just tried

[vivid ivy]

@raw kelp CodeLLDB works btw
it wasn't detecting sources because I was injecting the dll in the process using manual mapping