The memory monitor seems more useful in detecting memory leaks (not to be confused with info leaks) rather than bounds issues. Using GFlags with either standard or full page heap verification is typically more than enough to identify most bugs.
If you’re unfamiliar with the way GFlags works, I’ve included a brief description of it in a recent article I wrote for http://www.corelan.be:
Hi Pyoor
I was studying Peach Fuzzer recently, your series of articles of this theme have helped me a lot. But, I still do not understand expressionSet and expressionGet in . Can you explain in detail, because the introduction on the Peach official website is very vague.
September 18th, 2013 on 7:51 am
Why are you not using the Memory Monitor? It seems a good addition that does not affect.
September 21st, 2013 on 1:12 am
Kinunt,
The memory monitor seems more useful in detecting memory leaks (not to be confused with info leaks) rather than bounds issues. Using GFlags with either standard or full page heap verification is typically more than enough to identify most bugs.
If you’re unfamiliar with the way GFlags works, I’ve included a brief description of it in a recent article I wrote for http://www.corelan.be:
https://www.corelan.be/index.php/2013/07/02/root-cause-analysis-integer-overflows/#Page_heap
April 24th, 2018 on 2:40 am
Hi Pyoor
I was studying Peach Fuzzer recently, your series of articles of this theme have helped me a lot. But, I still do not understand expressionSet and expressionGet in . Can you explain in detail, because the introduction on the Peach official website is very vague.