diff options
| author | Yip Coekjan <69834864+Coekjan@users.noreply.github.com> | 2024-05-25 19:57:35 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-05-25 13:57:35 +0200 |
| commit | ab9f848dcd8ab4b5e73aad22934eb47fae39252f (patch) | |
| tree | d6524896c00fc09183247e66f5e6f2228e4ca6c7 /docs | |
| parent | 1b3350437c0292ce0bd2d1947c2da201f7772ad8 (diff) | |
| download | box64-ab9f848dcd8ab4b5e73aad22934eb47fae39252f.tar.gz box64-ab9f848dcd8ab4b5e73aad22934eb47fae39252f.zip | |
Fix unclosed item list (#1532)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/box64.pod | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/box64.pod b/docs/box64.pod index 380df4d4..51451708 100644 --- a/docs/box64.pod +++ b/docs/box64.pod @@ -467,6 +467,8 @@ script. yyyy needs to be a full path to a valid x86_64 version of bash * 1 : Launch `gdb` when a segfault, bus error or illegal instruction signal is trapped, attached to the offending process and go in an endless loop, waiting. When in gdb, you need to find the correct thread yourself (the one with `my_box64signalhandler` in is stack) then probably need to `finish` 1 or 2 functions (inside `usleep(..)`) and then you'll be in `my_box64signalhandler`, just before the printf of the Segfault message. Then simply `set waiting=0` to exit the infinite loop. * 2 : Launch `gdbserver` when a segfault, bus error or illegal instruction signal is trapped, attached to the offending process, and go in an endless loop, waiting. Use `gdb /PATH/TO/box64` and then `target remote 127.0.0.1:1234` to connect to the gdbserver (or use actual IP if not on the machine). After that, the procedure is the same as with ` BOX64_JITGDB=1`. This mode can be usefullwhen programs redirect all console output to a file (like Unity3D Games) +=back + =head1 VARIABLES FOR ENVIRONMENT ONLY =over 8 |