diff options
| author | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 16:49:16 +0100 |
|---|---|---|
| committer | llzmb <46303940+llzmb@users.noreply.github.com> | 2021-12-02 16:49:16 +0100 |
| commit | d9e39be4e8dd0242877412d1a17589acc825292e (patch) | |
| tree | 5a14d4bd4a4ada94cdd9fe74ab6bf557aa5e3e66 /frida_mode/DEBUGGING.md | |
| parent | ca7144161f900a0f5c8b76922a0102fbcc291f2c (diff) | |
| download | afl++-d9e39be4e8dd0242877412d1a17589acc825292e.tar.gz | |
Remove the word "simply"
Diffstat (limited to 'frida_mode/DEBUGGING.md')
| -rw-r--r-- | frida_mode/DEBUGGING.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/frida_mode/DEBUGGING.md b/frida_mode/DEBUGGING.md index 9cdc5eb6..b703ae43 100644 --- a/frida_mode/DEBUGGING.md +++ b/frida_mode/DEBUGGING.md @@ -160,9 +160,9 @@ Lastly, if your defect only occurs when using `afl-fuzz` (e.g., when using shared memory mapping being created for it to record its data), it is possible to enable the creation of a core dump for post-mortem analysis. -Firstly, check if your `/proc/sys/kernel/core_pattern` configuration is simply -set to a filename (AFL++ encourages you to set it to the value `core` in any -case since it doesn't want any handler applications getting in the way). +Firstly, check if your `/proc/sys/kernel/core_pattern` configuration is set to a +filename (AFL++ encourages you to set it to the value `core` in any case since +it doesn't want any handler applications getting in the way). Next, set `ulimit -c unlimited` to remove any size limitations for core files. |