Skip to content
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

Code builded outside the application can't be debugged #97

Closed
prb28 opened this issue Oct 20, 2019 · 1 comment
Closed

Code builded outside the application can't be debugged #97

prb28 opened this issue Oct 20, 2019 · 1 comment
Assignees
Labels
bug
Milestone

Comments

@prb28
Copy link
Owner

@prb28 prb28 commented Oct 20, 2019

From Antiriad_UK on EAB.

I don't know if something has changed on 0.18 but my breakpoints are no longer working. If I download the example workspace and build/run within VSCode then it works ok. But if I compile outside of VSCode and then debug it stops on entry fine (and can single step). But any breakpoints I've set are ignored and if I hover over them in vscode it says "Debug information not resolved retrieved"

This is on Win10.

Here's an example, just create a batch file in the root of your example gencop workspace and run it to compile. Then run the debug from vscode and see if it stops and and/or gives the debug not resolved message above.

Code:

set ObjDir=Build
set OutDir=fs-uae\hd0

set BuildParam=-m68000 -Fhunk -linedebug
set LinkParam=-bamigahunk -Bstatic

bin\vasmm68k_mot.exe %BuildParam% -o %ObjDir%\gencop.o gencop.s
bin\vlink.exe %LinkParam% -o %OutDir%\gencop %ObjDir%\gencop.o

If I download the 0.17 example bundle/bin files and roll vscode back to 0.17 the above works. Hmm. Maybe something changed in file path/debug info code and it's no longer able to resolve paths?

@prb28 prb28 self-assigned this Oct 20, 2019
@prb28

This comment has been minimized.

Copy link
Owner Author

@prb28 prb28 commented Oct 20, 2019

Not a solution... but a workaround, add to launch.json configuration :

"sourceFileMap": {
   "C:": "c:"
}

Or any drive letter your sources are in.
The source file name matching has some issues on windows.
I'll fix that in next release.

@prb28 prb28 added the bug label Oct 20, 2019
prb28 added a commit that referenced this issue Oct 20, 2019
@prb28 prb28 closed this Oct 20, 2019
@prb28 prb28 added this to the 0.18.1 milestone Oct 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.