-
-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems and workarounds for debugging C3 on Windows #1646
Comments
What happens with the MSVC debugger in the first case. |
The MSVC debugger starts at the breakpoint unlike LLDB. |
Does compiling C with Clang give the right output then? |
Yeah, as it should on both C and C++. |
Could you perhaps create a small sample and dump the LLVM here for C and the corresponding C3 program? Maybe paste in a gist if it's too big. |
I'm sorry if this si frustrating to you. I'm a novice and I don't know how to make an LLVM dump, so i used llvm-pdbutil dump to get info about the PDB file and I got the following: llvm-pdbutil dump -summary main.pdb
The code is a simple Hello World:
If this isn't what you're looking for, let mw know what I should do. |
After watching the same pattern as with Zig (ziglang/zig#22039) I thought it could be an issue from LLVM, but with C3 there are other small issues added on top of it:
LLDB starts debugging the line AFTER the breakpoint. Now, this doesn't mean "line number" but code line, so the if developer wrote down the next code line 4 lines below, LLDB will jump 4 lines down.
Both LLDB and MSVC Debugger ignore module declarations (the thing at the top of the file) and imports. MSVC debugger jumps to the main function if there's a breakpoint on an import or module, LLDB looks for the next breakpoint and ends the debugging session if there's none.
The text was updated successfully, but these errors were encountered: