Re: whither stack traces?

exportML is setup to map uncaught exceptions to an exit with a  
failure status.
It does not print an exception trace, since people may want to run  
executables
in situations where I/O is not possible.  You can print your own  
trace using
the SMLofNJ.exnHistory function.  The Backtrace stuff provides a  
finer-grain
trace, but at a runtime performance cost.

	- John

On Nov 28, 2006, at 1:35 PM, Dave Herman wrote:

> When I use ml-build to create a heap and then run that heap image with
> sml @SMLload=file.heap, top-level exceptions appear to be silently
> dropped. I've noticed that in the REPL, there is some sort of  
> exception
> backtrace given. Scouring the web indicates that previous versions of
> SML/NJ included the SMLofNJ.Internals.BTrace.mode option as well as  
> the
> -Cinstrument.btrace-mode command-line argument, neither of which  
> appears
> to exist anymore. I also noticed via sml -H a tdp.instrument compiler
> switch, but couldn't find any documentation.
>
> How do I get backtraces for uncaught exceptions when running a heap  
> image?
>
> Thanks,
> Dave
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Smlnj-list mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/smlnj-list
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV