If you have say unit tests that are optionally included based on a define, and that happens to be an include thats relatively pathed upwards (e.g. ../testing/testing.dm), the debugger will fail to determine the proc ref for anything in that file.
Example project here (doesn't have a tasks.json so you gotta open/focus a DM file and then F5)
example.zip
Steps to reproduce:
- Extract example.zip somewhere
- Open as folder in VSC
- Open client.dm and testing.dm
- Try breakpointing
world.log << "Rawr!" in testing.dm and then F5 (with a dm file focused because no tasks.json) - will not work
- Try instead breakpointing
do_something() in client.dm, F5, and then step in to the breakpoint - will work fine
Workaround
Optionally including a non-relatively pathed upwards file works fine (e.g. if you move testing.dm into a folder under the client folder and update the include to #include "testing/testing.dm").
E.g. cmss13-devs/cmss13#12846
Let me know if this is actually a problem with something else (e.g. I need to make an issue in a different repo), or whatever I'm doing wrong.
If you have say unit tests that are optionally included based on a define, and that happens to be an include thats relatively pathed upwards (e.g.
../testing/testing.dm), the debugger will fail to determine the proc ref for anything in that file.Example project here (doesn't have a tasks.json so you gotta open/focus a DM file and then F5)
example.zip
Steps to reproduce:
world.log << "Rawr!"in testing.dm and then F5 (with a dm file focused because no tasks.json) - will not workdo_something()in client.dm, F5, and then step in to the breakpoint - will work fineWorkaround
Optionally including a non-relatively pathed upwards file works fine (e.g. if you move testing.dm into a folder under the client folder and update the include to
#include "testing/testing.dm").E.g. cmss13-devs/cmss13#12846
Let me know if this is actually a problem with something else (e.g. I need to make an issue in a different repo), or whatever I'm doing wrong.