1 August 2010 at 10:45pm
I just had the same problem, and even though this is an old thread, I just want to add a posible solution. You can always view the apache error log under linux with "tail -f /var/log/apache2/error.log". I'm not sure if there is a similar file/command for mac or windows... This error log will show the error you are looking for, the custom error logging that Aug suggested is not really working for this problem.