Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /sml/trunk/HISTORY
ViewVC logotype

Diff of /sml/trunk/HISTORY

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 677, Mon Jun 26 00:56:56 2000 UTC revision 682, Tue Jul 4 06:25:51 2000 UTC
# Line 13  Line 13 
13  Description:  Description:
14  ----------------------------------------------------------------------  ----------------------------------------------------------------------
15  Name: Matthias Blume  Name: Matthias Blume
16    Date: 2000/07/04 15:26:00
17    Tag: blume-20000704-trigger
18    Description:
19    
20    1. Improvements to CM manual.
21    2. SMLofNJ.Internals.BTrace.trigger reinstated as an alternative way
22       of getting a back-trace.  The function, when called, raises an
23       internal exception which explicitly carries the full back-trace history,
24       so it is unaffected by any intervening handle-raise pairs ("trivial"
25       or not).  The interactive loop will print that history once it arrives
26       at top level.
27       Short of having all exceptions implicitly carry the full history, the
28       recommended way of using this facility is:
29         - compile your program with instrumentation "on"
30         - run it, when it raises an exception, look at the history
31         - if the history is "cut off" because of some handler, go and modify
32           your program so that it explicitly calls BTrace.trigger
33         - recompile (still instrumented), and rerun; look at the full history
34    
35    ----------------------------------------------------------------------
36    Name: Matthias Blume
37    Date: 2000/07/03 15:36:00 JST
38    Tag: blume-20000702-manual
39    Description:
40    
41    Small corrections and updates to CM manual.
42    
43    ----------------------------------------------------------------------
44    Name: Matthias Blume
45    Date: 2000/06/29 16:04:00 JST
46    Tag: blume-20000629-yacctool
47    Description:
48    
49    Changes:
50    
51    1. Class "mlyacc" now takes separate arguments to pass options to
52       generated .sml- and .sig-files independently.
53    2. Corresponding CM manual updates.
54    3. BTrace module now also reports call sites.  (However, for loop clusters
55       it only shows from where the cluster was entered.)  There are associated
56       modifications to core.sml, internals.{sig,sml}, btrace.sml, and btimp.sml.
57    
58    ----------------------------------------------------------------------
59    Name: Matthias Blume
60    Date: 2000/06/27 16:51:00 JST
61    Tag: blume-20000627-noweb
62    Description:
63    
64    Changes:
65    
66     1. Implemented "subdir" and "witness" options for noweb tool.
67        This caused some slight internal changes in CM's tool implementation.
68     2. Fixed bug in "tool plugin" mechanism.  This is essentially cleaning
69        some remaining issues from earlier path anchor changes.
70     3. Updated CM manual accordingly.
71    
72     4. Changed implementation of back-tracing so that I now consider it
73        ready for prime-time.
74    
75        In particular, you don't have to explicitly trigger the back-trace
76        anymore.  Instead, if you are running BTrace-instrumented code and
77        there is an uncaught exception (regardless of whether or not it was
78        raised in instrumented code), the top-level evalloop will print
79        the back-trace.
80    
81        Features:
82    
83          - Instrumented and uninstrumented code work together seemlessly.
84            (Of course, uninstrumented code is never mentioned in actual
85             back-traces.)
86    
87          - Asymptotic time- and space-complexity of instrumented code is
88            equal to that of uninstrumented code.  (This means that
89            tail-recursion is preserved by the instrumentation phase.)
90    
91          - Modules whose code has been instrumented in different sessions
92            work together without problem.
93    
94          - There is no penalty whatsoever on uninstrumented code.
95    
96          - There is no penalty on "raise" expressions, even in
97            instrumented code.
98    
99        A potential bug (or perhaps it is a feature, too):
100    
101          A back-trace reaches no further than the outermost instrumented
102          non-trivial "raise".  Here, a "trivial" raise is one that is the
103          sole RHS of a "handle" rule.  Thus, back-traces reach trough
104    
105               <exp> handle e => raise e
106    
107          and even
108    
109               <exp> handle Foo => raise Bar
110    
111          and, of course, through
112    
113               <exp> handle Foo => ...
114    
115         if the exception was not Foo.
116    
117         Back-traces always reach right through any un-instrumented code
118         including any of its "handle" expressions, trivial or not.
119    
120       To try this out, do the following:
121    
122         - Erase all existing binfiles for your program.
123           (You may keep binfiles for those modules where you think you
124            definitely don't need back-tracing.)
125         - Turn on back-trace instrumentation:
126              SMLofNJ.Internals.BTrace.mode (SOME true);
127         - Recompile your program.  (I.e., run "CM.make" or "use".)
128         - You may now turn instrumentation off again (if you want):
129              SMLofNJ.Internals.BTrace.mode (SOME false);
130         - Run your program as usual.  If it raises an exception that
131           reaches the interactive toplevel, then a back-trace will
132           automatically be printed.  After that, the toplevel loop
133           will print the exception history as usual.
134    
135    ----------------------------------------------------------------------
136    Name: Matthias Blume
137  Date: 2000/06/26 09:56:46 JST  Date: 2000/06/26 09:56:46 JST
138  Tag: blume-20000626-setup  Tag: blume-20000626-setup
139  Description:  Description:

Legend:
Removed from v.677  
changed lines
  Added in v.682

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0