> it appears that starting with 3.10 stack traces for natively compiled
> executables will be available. thanks!
> one thing that I would love to see is being able to redirect this output:
> so that I can log both errors and their stack traces in a file for later
> examination, but still continue running.

I agree it would be nice, and this feature is on my "to do" list.  It
takes a bit of work to make the backtrace data available from Caml, though,
so don't expect this for 3.10.

> how do I get backtraces on exceptions in then top-level?
> I want to see something like:
> h called g on line 1
> g called f on line 1
> f raised invalid_argument on line 1

Currently, you cannot.  Conceivably, this would be the same mechanism
as outlined above (i.e. making backtrace data available from Caml).
However, you'd get a backtrace in terms of file names and line
numbers, which don't make that much sense for toplevel definitions.
Functions names don't really exist in compiled code.

- Xavier Leroy