Yashraj Kakkad

@nuta @castarco Any ideas on what I can contribute to further in the docs? Also @nuta thanks for preparing the outline! For a start, I thought maybe I can write...

Thanks for the wonderful explanation! I went through the paper and I came up with the following roadmap: - Figure out the value of `NUM_BYTES` - Initialize `shadow` elements as...

I started off with trying to write a simple implementation for the heap. ```c void shadow_chunk(struct malloc_chunk *chunk) { //Let's assume this function will take a chunk and mark appropriate...

As we're having bits in every shadow array element, they're more than sufficient to store all the possible states of the corresponding 8 bytes, including our custom defined invalid-address states...

Thanks for the green signal :)

I have a couple of points - 1. [Introducing these flags](https://github.com/yashrajkakkad/resea/blob/f58f5a3d375e44bf99bf3887e6292160ab1be07c/Makefile#L119-L125) in the Makefile is causing build errors. Please tell me if I did something wrong here. 2. I think...

Perhaps we need to map the regions of the heap, stack etc. appropriately into shadow memory. I went through [libs/resea/arch](https://github.com/nuta/resea/tree/master/libs/resea/arch) and from what I understand the starting position of heap...

Please ignore all the messages above except for the flags point (#1). I figured out that using `__heap` and `__heap_end` will do the job.

Yes, @nuta. I figured that out and wrote a simple implementation for the heap as well. It was fairly straightforward as everything was properly aligned to 8-bytes. I wrote these...

> I guess only `b[1]` become accessible while the current shadow memory implementation cannot handle this situation, right? Hmm, I have no idea for now. We need to take a...