Breakpoints are broken when compiling with /FC /d1trimfile flags

[Adarma]

Version: 0.9.14 ALPHA [b99e102]

What paths are supposed to go in File Path Map?
I have my exe and pdb here: c:\build\.
The source code cpp files are here: c:\develop\code\

I assumed the exe path goes in Source Path and the cpp path goes in Destination Path.
Is that correct? Or maybe Source Path is for the source code path... not sure

At the moment my breakpoints are not being hit and I'm guessing this is why. Maybe I'm wrong about that though.
In a previous version I had the breakpoints working and I'm not sure what I did to break it.

Thanks

[ryanfleury]

The File Path Map is used to redirect paths which are referenced from within debug information, to a different local path. So for example, if I am debugging an executable which was built on another machine, and its debug info refers to a file D:/foo/bar/baz.c in its line info, but I have that file in C:/x/baz.c stored locally, the File Path Map allows me to redirect references to the former, to the latter. This will enable stepping/breakpoints in that relocated file.

Can you provide more information about how you're building & debugging? That should let me help with the breakpoints not working.

[Adarma]

I'm building from a commandline with current directory c:\develop\code.
I run vcvarsall and then compile with cl using a .bat :

<SetupStuff>
pushd ..\..\build
cl <Args> ..\develop\code\main.cpp <MoreArgs>
popd

I just tried this:

• Unzipped 0.9.14 ALPHA to a new folder.
• Complied with /Od and ran in the debugger.
• Deleted everything from File Path Map.
• Launched and then paused (Halt all attached processes). I get a message Could not find "C:\build\main.cpp.
• Press Find alternative....
• Select C:\develop\code\main.cpp. (It would be nice if this interface could show somewhere a reminder of the file being looked for as it is blurred out behind it).

This opens the code and has the step cursor set. I can now step over, step into, step out fine. I can click next to the line number to set a breakpoint, but if I then Resume all processes, the breakpoint is not hit and it just runs normally.

The only way I can break is with the pause.

Thanks for the development and support

[Adarma]

I think I found the problem.

Above I omitted defining the specfic <ARGS> used in the build to minimise the report as I thought they were all fairly standard and irrelevant. I'd missed that I used the cl flag /FC for full path diagnostics, but also /d1trimfile:%CD%\ to strip the current directory from the __FILE__ macro.

If I remove that flag the breakpoints work again, but my __FILE__ macro values are absolute.

[ryanfleury]

Treatment of /d1trimfile has been fixed up (to the degree possible) as of 0.9.19. It may still require an initial file selection, because the debugger does not necessarily know from which directory the paths are relative (the only path it starts with is the EXE's), but after that point, it should correctly work.

[Adarma]

Great, thanks! It is working well

[Adarma]

This seems to have regressed in 0.9.21 ALPHA 7be1faa. Breakpoints are only working when I remove the /d1trimfile arg