Skip to content

Commit 7324c71

Browse files
committed
add: finished the paper
1 parent d48121a commit 7324c71

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

71 files changed

+3386
-742
lines changed

README.md

Lines changed: 26 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,26 @@
1-
# Nuculeo-VSExtension
2-
3-
### Cose interessanti
4-
5-
- referencesViews.ts: `void vscode.commands.executeCommand('setContext', 'cpptools.hasReferencesResults', hasResults);`
6-
-
7-
8-
9-
### Importante
10-
11-
- gli eseguibili in bin/ e le cartelle LLVM/ e debugAdapters/ non vengono fornite dalla microsoft e ogni cambio di release andranno copiate e incollate a mano nella cartella Extensions/ prima di lanciare il comando di build `vsce package`
12-
13-
14-
15-
### Strutturra della tesi
16-
17-
Aggiungere istruzioni:
18-
- uso
19-
- come aggiungere funzionalitá
20-
- come installare l'ambiente di sviluppo
21-
- come debuggare l'estensione
22-
- come pubblicarla?
23-
- come fare il pacchetto vsix
24-
################################################################################
25-
26-
27-
1+
# VSCode nucleo debugger
2+
3+
### Risorse
4+
https://en.wikipedia.org/wiki/GNU_Debugger
5+
https://sourceware.org/gdb/current/onlinedocs/gdb.html/Python-API.html
6+
https://en.wikipedia.org/wiki/QEMU
7+
8+
https://microsoft.github.io/debug-adapter-protocol/specification#Requests_Evaluate
9+
https://microsoft.github.io/debug-adapter-protocol/overview
10+
https://github.com/microsoft/VSDebugAdapterHost/tree/main
11+
12+
https://code.visualstudio.com/api/get-started/your-first-extension
13+
https://github.com/microsoft/vscode-extension-samples?tab=readme-ov-file
14+
https://vscode-api.js.org
15+
https://code.visualstudio.com/api/
16+
https://code.visualstudio.com/Docs/editor/tasks
17+
https://code.visualstudio.com/api/extension-guides/webview
18+
https://code.visualstudio.com/Docs/editor/debugging
19+
https://code.visualstudio.com/api/extension-guides/debugger-extension
20+
https://github.com/SolarTheory/Microsoft-VSCode-Codicons
21+
https://code.visualstudio.com/api/working-with-extensions/publishing-extension
22+
https://code.visualstudio.com/api/extension-guides/command
23+
https://stackoverflow.com/questions/61705879/code-inside-activate-function-of-vs-code-extension-is-not-run
24+
https://code.visualstudio.com/api/references/activation-events#onDebug
25+
https://www.typescriptlang.org/docs/
26+
https://handlebarsjs.com/

nucleo-debugger/LICENSE.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
yes

nucleo-debugger/README.md

Lines changed: 0 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,71 +1 @@
11
# nucleo-debugger README
2-
3-
This is the README for your extension "nucleo-debugger". After writing up a brief description, we recommend including the following sections.
4-
5-
## Features
6-
7-
Describe specific features of your extension including screenshots of your extension in action. Image paths are relative to this README file.
8-
9-
For example if there is an image subfolder under your extension project workspace:
10-
11-
\!\[feature X\]\(images/feature-x.png\)
12-
13-
> Tip: Many popular extensions utilize animations. This is an excellent way to show off your extension! We recommend short, focused animations that are easy to follow.
14-
15-
## Requirements
16-
17-
If you have any requirements or dependencies, add a section describing those and how to install and configure them.
18-
19-
## Extension Settings
20-
21-
Include if your extension adds any VS Code settings through the `contributes.configuration` extension point.
22-
23-
For example:
24-
25-
This extension contributes the following settings:
26-
27-
* `myExtension.enable`: Enable/disable this extension.
28-
* `myExtension.thing`: Set to `blah` to do something.
29-
30-
## Known Issues
31-
32-
Calling out known issues can help limit users opening duplicate issues against your extension.
33-
34-
## Release Notes
35-
36-
Users appreciate release notes as you update your extension.
37-
38-
### 1.0.0
39-
40-
Initial release of ...
41-
42-
### 1.0.1
43-
44-
Fixed issue #.
45-
46-
### 1.1.0
47-
48-
Added features X, Y, and Z.
49-
50-
---
51-
52-
## Following extension guidelines
53-
54-
Ensure that you've read through the extensions guidelines and follow the best practices for creating your extension.
55-
56-
* [Extension Guidelines](https://code.visualstudio.com/api/references/extension-guidelines)
57-
58-
## Working with Markdown
59-
60-
You can author your README using Visual Studio Code. Here are some useful editor keyboard shortcuts:
61-
62-
* Split the editor (`Cmd+\` on macOS or `Ctrl+\` on Windows and Linux).
63-
* Toggle preview (`Shift+Cmd+V` on macOS or `Shift+Ctrl+V` on Windows and Linux).
64-
* Press `Ctrl+Space` (Windows, Linux, macOS) to see a list of Markdown snippets.
65-
66-
## For more information
67-
68-
* [Visual Studio Code's Markdown Support](http://code.visualstudio.com/docs/languages/markdown)
69-
* [Markdown Syntax Reference](https://help.github.com/articles/markdown-basics/)
70-
71-
**Enjoy!**
3.24 MB
Binary file not shown.

nucleo-debugger/out/nucleoweb.js

Lines changed: 14 additions & 11 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

nucleo-debugger/out/nucleoweb.js.map

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

nucleo-debugger/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,11 +7,11 @@
77
"engines": {
88
"vscode": "^1.91.0"
99
},
10+
"publisher": "UniPi - Giuseppe Lettieri",
1011
"author": {
1112
"name": "Giuseppe Lettieri"
1213
},
1314
"categories": [
14-
"Programming Languages",
1515
"Debuggers",
1616
"Other"
1717
],

0 commit comments

Comments
 (0)