Breakpoints seem to not be triggered correctly #457
Description
This bug happens when I am using Jai and building my project in a particular way. For some reason it seems the '../' in the file path might be tripping up both RAD Debugger and RemedyBG. Visual Studio 2022 does not seem to have this behavior and acts as I would expect.
I have included a zip file with the source code for the repro, seeing as the compiler is in closed beta still, I can send the pre-built binaries if needed
There is a how_to_repro.txt in the included zip file, but here is a copy of the steps to reproduce:
This bug seems to happen in both RAD Debugger and RemedyBG, but not in Visual Studio 2022.
It could just be a compiler bug. But since Visual Studio acts how I would expect I am less
inclined to believe that is the case:
For reference, this is the version information found in the help tab:
The RAD Debugger (0.9.15 ALPHA) - Mar 26 2025 [33326a8f] [Debug]
1.) Build the jai code by running:
jai first.jai
(NOTE: The version of the Jai compiler I am using to build this repro is: beta 0.2.010, built on 4 March 2025)
2.) Open raddbg, add 'raddbg_breakpoint_repro.exe' as a target
3.) Open the two files in the source window 'src/platform/windows/entry.jai' and 'src/renderer/vulkan/redner_backend.jai'
4.) Place a breakpoint on the print statement at line 4 in 'render_backend.jai'
5.) Run the program in raddbg and see that the breakpoint is not stopped on
6.) Place a breakpoint on line 3 in 'entry.jai'
7.) Rerun raddbg and see that the breakpoint in main is correctly stopped on, but when hitting F5 to continue, the previous breakpoint still is not stopped at