@@ -36,6 +36,22 @@ about memory usage, allowing to track down which parts of the program consumes
36
36
the most memory.
37
37
This is very useful to resolve unexpected memory consumption issues.
38
38
39
+ ## Getting symbolic backtrace
40
+
41
+ To get a symbolic backtrace you need the debug information files. For the
42
+ release you can download them from
43
+ [ GitHub Release] ( https://github.com/AdaCore/ada_language_server/releases )
44
+ Assets. Assets contain an archive per platform with the ALS
45
+ executable and debug information files (` .debug ` file on Linux/Windows and
46
+ ` .dSYM ` directory for Mac OS X). Extract the debug information to the directory
47
+ containing ALS (usually this is
48
+ ` $HOME/.vscode/extensions/adacore.ada-*/{darwin,linux,win32} ` )
49
+ and run
50
+
51
+ addr2line ada_language_server <hex backtrace>
52
+
53
+ On Mac OX X use [ atos] ( https://www.unix.com/man-page/osx/1/atos/ ) instead.
54
+
39
55
### Writing tests
40
56
41
57
To write a functional test for Ada Language Server:
@@ -116,16 +132,16 @@ Release notes
116
132
```
117
133
118
134
Then push it to GitHub with `git push 22.0.3` or `git push --tags`.
119
- The travis CI will publish the extension on the marketplace.
135
+ The GitHub CI will publish the extension on the marketplace and the
136
+ [Open VSX Registry](https://open-vsx.org). It also makes GitHub Release and
137
+ put archives with ALS executables and debug information files.
120
138
121
139
## Source directories
122
140
123
141
The repository contains the following folders:
124
142
125
143
* `doc/` - documentation of the project and LSP extensions
126
144
* `gnat/` - GNAT project files
127
- * `integration/appveyor/` - Appveyor CI (Windows) integration scripts
128
- * `integration/travis/` - Travis CI (Linux and Mac OS) integration scripts
129
145
* `integration/vscode/ada/` - VS Code extension sources
130
146
* `scripts/` - some support scripts
131
147
* `ada_language_server/source/ada/` - LSP implementation for Ada language
0 commit comments