-
Notifications
You must be signed in to change notification settings - Fork 62
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
[Bug]: ALS ada log file scrambled (multi-tasking?) #1235
Comments
This issue does not happen with release 26.0.202411173. |
Hello @simonjwright , Thank you for the report. The default log file name is A workaround is to edit your
Does that yield two log files in your use case? Also to understand a bit more |
I did what you suggested (are you sure about the second I tried another project without the possibly-problematic nested test project arrangement, and after a lot of trouble with vscode remembering far too much about previously-opened projects it opened with only one log file. I then tried ada-ts-mode. It did open two log files, the first when I opened a file in I think the ada-ts-mode problem arises when the 'other' file has to be opened - getting info about e.g. an Ada object in the other file isn’t a problem. |
Hi @simonjwright , Note that we now append the PID after the timestamp to the ALS log file names by default, to avoid any potential collision. Regards, |
Environment
Bug Summary and Reproducer
Bug Summary: The [ALS PROJECT] and later [ALS.MAIN] sections of the log are scrambled so they’re very hard to read.
One possibly unusual thing: this project (esp32h2_hal) contains a nested
test
project, which refers to the parent project via a pin. Using VSCode, everything works fine (in spite of the scrambled log!), but using ada-ts-mode, when I navigate from a file inesp32h2_hal/test/
to a file in the parentesp32h2_hal/
another ALS is spawned which doesn’t know about settings (e.g. runtime) in the original. I’m trying to debug this undesirable behaviour.Steps to reproduce:
$ code test.adb
Expected behavior:
The log file isn’t corrupted.
Configuration and Logs
Other VS Code Extensions
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: