I've done work in troubleshooting for over a decade. Your comment "any dodgy/corrupt file will do" would drive me insane. You need concrete examples to troubleshoot software. Without it, you can't be sure if you're solving the actual issue or a new issue.
What you've described sounds like an honest attempt to determine what the problem actually is.
Look at it this way: your problem is that the reader will hang if reading a corrupt file. Without concrete examples, it becomes more of a general problem then a specific one. And in my experience specific problems will always get more attention then general.
Last edited by ottdmk; 11-28-2012 at 02:08 PM.
|