You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/user-guide/inspecting.md
+14-3Lines changed: 14 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,21 @@
1
1
# Inspecting results
2
2
3
-
## g2html
3
+
## HTML
4
+
1. Run Goblint with additional `--html` argument.
5
+
2. Run `python3 -m http.server --directory result 8080`
6
+
or `npx http-server -c-1 result`.
7
+
3. Inspect results at <http://localhost:8080/index.xml>.
8
+
9
+
Modern browsers' security settings forbid some file access which is necessary for the HTML output to work, hence the need for serving the results via Python's `http.server` (or similar).
10
+
11
+
## g2html (legacy)
12
+
If there are problems with the above HTML output, the legacy g2html output (using an external Java component) is still possible.
13
+
The frontend of the above HTML output is reused from g2html, so the two look the same (except for code highlighting).
14
+
4
15
1. First time run: `make jar`.
5
-
2. Run Goblint with additional `--html` argument.
16
+
2. Run Goblint with additional `--set result g2html` arguments.
6
17
3. Run `python3 -m http.server --directory result 8080`
7
-
or `npx http-server -c-1 result`.
18
+
or `npx http-server -c-1 result`.
8
19
4. Inspect results at <http://localhost:8080/index.xml>.
9
20
10
21
Modern browsers' security settings forbid some file access which is necessary for g2html to work, hence the need for serving the results via Python's `http.server` (or similar).
0 commit comments