Re: Core Data Reverse Engineering KickStarter Project
Re: Core Data Reverse Engineering KickStarter Project
- Subject: Re: Core Data Reverse Engineering KickStarter Project
- From: Michael Crawford <email@hidden>
- Date: Tue, 25 Jun 2013 19:31:50 -0700
On 6/25/13, Scott Ribe <email@hidden> 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
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden