David Nadlinger: > Sorry, I don't quite understand the problem â the exception message > describes what happened, and the stack trace points to the location. The > only thing that strikes me as strange here is that file.foo itself isn't > included in the backtrace,
Right, that's my problem. I'd like to know the function and line number where the File constructor is called. > but I'd say that's a bug in the exception > handling code, not related to File itself. Or did I miss anything? You are probably right that File is not the cause of the problem. > By the way, this is how the output looks on OS X: > ... > No line numbers, unfortunately, but the whole call stack is present. Such stack trace is more than enough for me :-) But the implementation of exception handling differs between different operating systems, so I don't know if there is a bug in the Windows stack frame printing, or if there is a more structural problem that can't be solved. I will probably file a bug report for this Windows stack frame, then. Bye and thank you, bearophile
