Yan Shoshitaishvili
Yan Shoshitaishvili
Is your usecase the reading and writing of a file from the same path? This is something that's (surprisingly) not possible with the current approach -- the actual file contents...
Are we sure we need this? The only people that will likely be diving through pyvex code is us anyways, and we can make ad hoc changes to the flags...
If you think you'll save more time building in build profile detection than changing the compiler flags when needed, then it makes sense of course. I'm not so sure that...
Hahahaha, fair point :-)
This sounds like a bug in simuvex. Could you create a `test.py` that triggers this?
Wow, thank you for that awesome answer, @schieb! Andrew tagged it with add-to-docs, which is an excellent idea. We'll leave the issue open until that happens :-)
The likely scenario is that we won't get around to this until it becomes an immediate issue for us in terms of some research scenario, but miracles do happen. :-)...
It looks like some underlying API in CLE changed as well. When I change it to `keys`, I get: ``` In [4]: s.memory.dbg_print() --------------------------------------------------------------------------- AttributeError Traceback (most recent call last)...
Intersting... Would you mind sending along a PR so that we can play around with it?
You can enable fast memory mode by using the `FAST_MEMORY` state option. This will make SimuVEX use a different memory storage backend that is really only heavily tested for registers...