8
edits
Changes
→Updates for weeks: 2014-09-26, 2014-10-03, 2014-10-10 and 2014-10-17
== Updates ==
=== 2014-10-17 ===
Summary of the week and Meeting:
* Update on Linux status: almost done, needs testing and better error handling.
* Update on memory interface decisions: Sometimes a memory region will cease to exist before we finish traversing it. Now if we fail, we get the next available memory region starting from the failed address, and retry to read the memory 5 times before skipping the region.
* We decided to make a WalkMemory function that traverses the memory and applies a given function to each memory blocks (memory block size is defined as a parameter to WalkMemory, and each block overlap by half it size).
* We talked about the test case with python socket.recvfrom_into: It is possible to do, but we have to know how to find the function names table in memory, to know if a program is calling that function.
* Go forbidding passing Go pointers to C: ([https://code.google.com/p/go/issues/detail?id=8310 Go Issue]). We decided to wait for the proposal from the Go team to see how much does it affect us.
* There's a working example of the memsearch functionality in the "examples" folder. It is working in Windows.
* We have to define our deadlines for presenting the project in our university and doing a presentation to the Mozilla Team.
=== 2014-10-10 ===
We worked on a Go interface for memory access (Process interface), and polished the C interface.
* Mac code for memory access was working this week.
* We found out that Go has a [https://code.google.com/p/go/issues/detail?id=8921 bug using Windows HANDLE's]. So Windows code was not working.
* Started refactor of Linux memory access to use the Process interface.
* Three weeks to finish memsearch.
=== 2014-10-03 ===
No meeting this week. We continued working in the Mac and Windows memory access interface. We decided to do more things in Go than in C because the performance penalty of using CGO is not that big.
=== 2014-09-26 ===
Summary of the week and Meeting:
* We started defining a memory access interface in C for both Mac OS and Windows.
* Testing: Created a go test for searching known byte sequences in memory, and discussed how to organize tests in the future, probably the best would be to use a script for compiling and running the binaries. Right now our test spawns a child process and searches in its memory, we want to test on a non-related process.
* Discussed a bit more about in-memory encoding issues. Pato will write a document with his ideas. We decided to use a normal Go regexp and ignore encoding issues for now.
=== 2014-09-19 ===
