search

rlarranaga / bafprp

Automatically exported from code.google.com/p/bafprp
0 stars 0 forks source link

Make bafprp more resilient to random vendor header data #29

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
It has been frequently reported that certain vendors will prepend useless 
information onto baf files.  This causes bafprp to choke because it expects a 
clean baf file with a standard entry point.
It is theoretically possible to help mitigate this problem for new users by 
adding some code that will simply scan the file to find the first valid looking 
entry point and start from there.
Bafprp should be able to find valid enough looking entry points to help ease 
new users into using the software.  A big huge warning message should be 
printed to tell users of the problem, but bafprp should be able to handle at 
least a little bit of vendor trickery.

Original issue reported on code.google.com by charless...@gmail.com on 28 Oct 2010 at 9:15

GoogleCodeExporter commented 9 years ago 
Going to mark this one as fixed due to the changes I made in r228 - r233

Original comment by charless...@gmail.com on 3 Jan 2013 at 5:56