[Xsb-commits] CVS: XSB/docs/userman exceptions.tex,1.9,1.10

[David S. W. <dw...@us...>]

Update of /cvsroot/xsb/XSB/docs/userman
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv25916/userman

Modified Files:
	exceptions.tex 
Log Message:
Added paragraph on backtrace printed when XSB receives an interrupt.
And indicated that xsb_backtrace should be imported from machine.


Index: exceptions.tex
===================================================================
RCS file: /cvsroot/xsb/XSB/docs/userman/exceptions.tex,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- exceptions.tex	23 May 2006 00:00:51 -0000	1.9
+++ exceptions.tex	22 Jun 2006 21:03:20 -0000	1.10
@@ -272,6 +272,14 @@
 We are, however, in the process of reclassifying errors to their ISO
 types.
 
+When XSB generates a memory exception, it prints out a backtrace and
+exits.  This should be caused only by a bug in XSB or included code.
+The first predicate in the backtrace that is printed in these
+circumstances may be incorrect or redundant.  This is becasue the
+memory structures used to generate the backtrace are not always
+completely consistent, and so an interrupt at an unexpected point may
+result in the use of somewhat inconsistent information.
+
 %---------------------------------------------------------------------------------------
 \section{Predicates to Throw and Handle Errors}
 \label{sec:errorpredicates}
@@ -518,7 +526,7 @@
 can be used to manipulate backtraces.
 
 \begin{description}
-\ournewitem{xsb\_backtrace(-Backtrace)}{error\_handler}
+\ournewitem{xsb\_backtrace(-Backtrace)}{machine}
 \index{\texttt{xsb\_backtrace/1}}
 Upon success {\tt Backtrace} is bound to a structure indicating the
 forward continuations for a point of execution.  This structure should