Paul is explaining that your proposed solution, inspecting the call stack, is something that can only be done AFTER compilation, and it for identifying runtime errors, not compilation errors.
A compilation error means you cannot run the process.
@postwick Unfortunately I too have had this issue and its indeed very nasty to solve.
The only effective way I have found to do it is commit all my code, then start deleting large parts of it until the compilation error goes away.