#1 Burning Software

I have a ripping app which crashes when it tries to read the ToC from CDs with a high track count (90+). I have stepped through the code in the debugger and it behaves very oddly. The call to StarBurn_CdvdBurnerGrabber_GetTOCInformation() returns EN_SUCCES, and the stack doesn't *seem* to be corrupted, but the program inevitably encounters an access violation shortly after that call (no matter how many lines of code I skip). Any thoughts? It looks like the StarBurn ToC data structure supports up to 100 tracks, but is the actual limit lower then that?

Well, I have answered this one myself with a little extra digging! The answer is... yes. There is a buffer overflow somewhere in StarBurn_CdvdBurnerGrabber_GetTOCInformation(). If you just pass it a pointer to a TOC_INFORMATION structure, it will gladly wirte past the end of it. I have verified this by passing it a much larger buffer (32kB) and everything worked fine.... Until I called StarBurn_CdvdBurnerGrabber_GrabTrack() which apperently calls StarBurn_CdvdBurnerGrabber_GetTOCInformation() internally and presumably only passes in a buffer of size sizeof(TOC_INFORMATION). So this is a pretty critical bug for me... What are the chances of getting a patch for this?

This is known issue and it's fixed already in RC. Please drop us a message to info@rocketdivision.com and we'd provide you with a test build facing this (and other) issues. Thanks!