On 6/25/13, Scott Ribe <scott_r...@elevated-dev.com> wrote: > This is what I've been thinking--with the importer asserted to a crazy > extent, so that you get notified of anything that it doesn't completely > understand.
Using assertions in an importer is one of my more-effective reverse engineering techniques. Take a guess at the document format. Write an importer that reads that format. Put assertions everywhere. If your first guess is wrong, you'll trip an assertion. Lather. Rinse. Repeat. The other thing I do is run the importer under Valgrind. That will even flag out-of-bound reads by so much as one byte. Valgrind includes a machine code interpreter, that validates every memory access, before passing system and library calls off to native code. -- Michael David Crawford mdcrawf...@gmail.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
