Romain Malmain
Romain Malmain
thank you for the detailed report. i just saw you closed the issue, is it because your problem is solved?
it makes sense to me that you get the segfault at least since shadow memory is designed to work with memory in the `[0x10007fff8000, 0x7fffffffffff]` range (for high addresses), and...
ok thanks. i tried to check online for this address (`0xaaaaaaaaa000`) but nothing interesting so far.
as far as i understand the stop event is not created at all so far, why would you need to ask for stopping the fuzzer from the state? also there...
I don't think so, we don't have access to the state from the signal handler. i don't think it is easy to fix, since we could have a signal happening...
yes, it can be interesting to link this to state. but it should not be mixed with signal handling. so maybe just refactor `Restartable` to get / set the static...
> if that's your goal, how about doing it like > > ``` > (inside libafl_sugar) > if opt.use_snapshot { > let module = tuple!(x, y, snapshot); > // continue...
> > in term of performance, the extra check would only be noticeable in pre_exec / post_exec, which should be fine in most cases. > > but for example in...
> https://github.com/AFLplusplus/LibAFL/blob/poc/crates/libafl_sugar/src/qemu.rs > > I have a solution using macros 😜 yeah i saw, i don't want to maintain this kind of macro, they tend to become unreadable. this part...
i am in the middle of refactoring for this part of the code (#3159). this specific function will most likely disappear. i was planning to add a callback to set...