about summary refs log tree commit diff
path: root/qemu_mode/README.wine.md
diff options
context:
space:
mode:
authorllzmb <46303940+llzmb@users.noreply.github.com>2021-11-25 16:33:29 +0100
committerllzmb <46303940+llzmb@users.noreply.github.com>2021-11-25 16:33:29 +0100
commit1a57253a1c63315b5af8fdbe5081492ce0603278 (patch)
treed0893b756c403361ea76dec62c645fe516976d80 /qemu_mode/README.wine.md
parentce21346053b5624a8cb76541e665662f8f40741c (diff)
downloadafl++-1a57253a1c63315b5af8fdbe5081492ce0603278.tar.gz
Edit QEMU mode READMEs
Diffstat (limited to 'qemu_mode/README.wine.md')
-rw-r--r--qemu_mode/README.wine.md30
1 files changed, 16 insertions, 14 deletions
diff --git a/qemu_mode/README.wine.md b/qemu_mode/README.wine.md
index 567901cd..ee1ef58a 100644
--- a/qemu_mode/README.wine.md
+++ b/qemu_mode/README.wine.md
@@ -1,21 +1,23 @@
 # How to troubleshoot AFL++'s wine mode
 
 ## 1) Debugging
-To turn on wine debugging use the `WINEDEBUG` environment variable, 
-e.g. `WINEDEBUG=+timestamp,+tid,+loaddll`. 
+
+To turn on wine debugging, use the `WINEDEBUG` environment variable, e.g.,
+`WINEDEBUG=+timestamp,+tid,+loaddll`.
 
 ## 2) LoadLibraryA workaround
-The forked process fails to load libraries loaded via `LoadLibrary` 
-if the load happens after the entry point (error code: 87). To resolve 
-this issue, one needs to load any external libraries before the fork happens.
 
-An early DLL load can be achieved by adding the DLL name into the `Import Directory`
-in the PE file. Such an entry can be added manually in any PE editor. 
+The forked process fails to load libraries loaded via `LoadLibrary` if the load
+happens after the entry point (error code: 87). To resolve this issue, one needs
+to load any external libraries before the fork happens.
+
+An early DLL load can be achieved by adding the DLL name into the `Import
+Directory` in the PE file. Such an entry can be added manually in any PE editor.
 
-Alternativly, one can generate a `.lib` file from the DLL exports and link 
-them together with the harness to create an entry in the `Import Directory`. 
-Use `dumpbin /exports <filename>.dll` to extract the exports and paste the 
-exported function names into a `.def` file. Use `lib /def:<deffile> /OUT:<libfile>`
-to generate a `.lib` and add the library to the linker options. Once the usage of 
-an export is detected (`__declspec(dllimport)`), the
-linker adds the early DLL load.
\ No newline at end of file
+Alternatively, one can generate a `.lib` file from the DLL exports and link them
+together with the harness to create an entry in the `Import Directory`. Use
+`dumpbin /exports <filename>.dll` to extract the exports and paste the exported
+function names into a `.def` file. Use `lib /def:<deffile> /OUT:<libfile>` to
+generate a `.lib` and add the library to the linker options. Once the usage of
+an export is detected (`__declspec(dllimport)`), the linker adds the early DLL
+load.
\ No newline at end of file