m4b

I'll check out layer/region; I'm mostly concerned about how to extensibly add values to the memory range data structure; probably enum is best. Specifically, the approach that BAP takes is...

While I'm dispensing unsolicited opinions ;) i'm on the fence about this. On one hand its very popular, and makes easy integration with other crates, on other, e.g., in https://github.com/m4b/scroll,...

Hehe yea. Probably actually makes more sense to use the calculator when / if a scripting language lands as it will be a more unified interface. Then again sometimes I...

Uh yea that sounds awesome! The spacebar is totally great idea, quick concise, easily available and easy to remember. I like the notation system as well, especially temp variables (in...

Hmmm yea that's probably the easiest. Perhaps we should make the disassembly step after loading lazy though as loading several architectures eagerly probably doesn't make a lot of sense. Perhaps...

Yea, I was specifically worried about the i386 and x86_64 fat binaries, which are usually the system libraries like `libSystem_B.dylib`, et. al. Seems a waste to load the i386 and...

Oh dear; I believe I've just found the issue, and it's right here in this equation: ``` 224 * 3000 * 1800 = 1209600000 = 1.2GB ``` for libc, I...

Soooo I already did this cause I got bored one fine Sunday. I'll post the work in progress here, or open a new issue so you can see what I...

Good idea, in fact, when we do the refactor we should make statements have that exact API so any changes underneath are completely invisible to clients. For now using Vec...

Here is the experimental "binary RREIL" encoding I mentioned, which uses 27 bytes per Statement (compared to previous 220): ```rust use scroll::{Pread, Gread, Pwrite, Gwrite}; use {Result, Rvalue, Lvalue, Statement};...