Menu
▾
▴
clisp-cvs Digest, Vol 55, Issue 2
|
From: <cli...@li...> - 2010-12-15 01:04:58
|
Send clisp-cvs mailing list submissions to cli...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/clisp-cvs or, via email, send a message with subject or body 'help' to cli...@li... You can reach the person managing the list at cli...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of clisp-cvs digest..." CLISP CVS commits for today Today's Topics: 1. clisp/doc impext.xml,1.661,1.662 (Sam Steingold) 2. clisp/doc impbody.xml,1.611,1.612 impent.xml,1.384,1.385 (Sam Steingold) 3. clisp/doc impbody.xml,1.612,1.613 (Sam Steingold) ---------------------------------------------------------------------- Message: 1 Date: Wed, 03 Nov 2010 16:34:56 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impext.xml,1.661,1.662 To: cli...@li... Message-ID: <E1P...@sf...> Update of /cvsroot/clisp/clisp/doc In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv5374 Modified Files: impext.xml Log Message: fix validity Index: impext.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impext.xml,v retrieving revision 1.661 retrieving revision 1.662 diff -u -d -r1.661 -r1.662 --- impext.xml 1 Nov 2010 18:20:43 -0000 1.661 +++ impext.xml 3 Nov 2010 16:34:53 -0000 1.662 @@ -4999,7 +4999,7 @@ wakeup</ulink>s, i.e., this function may return &t; even though no thread called &exemption-broadcast; or &exemption-signal;. Therefore, a common idiom for using this function is: <code>(&loop; - :until (&pred-r;) :do (&exemption-wait; &exemp-r; &mutex-r;))</code> + :until (&pred-r;) :do (&exemption-wait; &exemp-r; &mutex-r;))</code></para> <simpara>The &test-k; argument simplifies this. When supplied, &exemption-wait; returns when either &test-k; &pred-r; is satisfied (always called while &mutex-r; is held) or when &timeout-k; elapses. @@ -5008,7 +5008,7 @@ When &test-k; is supplied, &exemption-wait; returns &t; when &exemp-r; was signaled and &test-k; &pred-r; is satisfied and &nil; on timeout. </simpara><simpara>This is the preferred and most portable way to wait on - an exemption.</simpara></para> + an exemption.</simpara> <simpara>Cf. <function role="unix">pthread_cond_wait</function>.</simpara> </listitem></varlistentry> <varlistentry id="exemption-broadcast"><term><code>(&exemption-broadcast; ------------------------------ Message: 2 Date: Wed, 03 Nov 2010 16:47:20 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impbody.xml,1.611,1.612 impent.xml,1.384,1.385 To: cli...@li... Message-ID: <E1P...@sf...> Update of /cvsroot/clisp/clisp/doc In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv7587/doc Modified Files: impbody.xml impent.xml Log Message: document show-stack Index: impbody.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v retrieving revision 1.611 retrieving revision 1.612 diff -u -d -r1.611 -r1.612 --- impbody.xml 20 Sep 2010 20:40:23 -0000 1.611 +++ impbody.xml 3 Nov 2010 16:47:18 -0000 1.612 @@ -1332,7 +1332,7 @@ <formalpara id="err-pr-bt"><title>Variable &err-pr-bt;</title> <para>When this variable is non-&nil; the error message printed by - &abort-on-error; and &exit-on-error; includes the backtrace (stack). + &abort-on-error; and &exit-on-error; includes the &backtrace; (stack). </para></formalpara> <formalpara id="global-handler"><title>Function &set-global-handler;</title> @@ -2131,7 +2131,7 @@ precision contagion: set it to &t; to have &clisp; &signal; a &warning-t; on float precision contagion; set it to &error; to have &clisp; &signal; an &error-t; on float precision contagion, so that you - can look at the stack backtrace.</para></simplesect> + can look at the stack &backtrace;.</para></simplesect> </section> @@ -2163,7 +2163,7 @@ would be possible: set it to &t; to have &clisp; &signal; a &warning-t; in such situations; set it to &error; to have &clisp; &signal; an &error-t; in such situations, so that you can look at the stack - backtrace.</para></simplesect> + &backtrace;.</para></simplesect> <simplesect id="phasecont"><title>Variable &phasecont;</title> <para>A similar variable, &phasecont;, controls the return @@ -5600,9 +5600,10 @@ below the frame that corresponds to the form or the function call that binds that variable.</para> +<formalpara id="stack-mode"><title>Stack Printing Mode</title> <para>There is a current <firstterm>stack mode</firstterm> which defines in how much detail the stack is shown by the stack-related debugger - commands:<orderedlist> + commands (&backtrace; et al):<orderedlist> <listitem><simpara>All the stack elements are considered. This mode works fine for debugging compiled functions.</simpara></listitem> <listitem><simpara>All the frames are considered.</simpara></listitem> @@ -5614,7 +5615,7 @@ <listitem><simpara>Only &apply; frames are considered. Every invocation of an interpreted function corresponds to one &apply; frame.</simpara></listitem> -</orderedlist></para> +</orderedlist></para></formalpara> <table id="debugger-deb-step-1" frame="all"> <title>Commands common to the debugger and the stepper</title> @@ -5643,17 +5644,18 @@ <entry><command>:b</command></entry> <entry>goes to bottom (most recent) frame, i.e., most probably to the form or function that caused the debugger to be entered.</entry></row> - <row><entry><command>Mode</command> &mode-r;</entry> - <entry><command>:m</command> &mode-r;</entry> - <entry>sets the current stack mode</entry></row> - <row><entry><command>Frame-limit</command> &l-r;</entry> + <row><entry><command>Mode</command> &stack-mode;</entry> + <entry><command>:m</command> &stack-mode;</entry> + <entry>sets the current stack printing mode</entry></row> + <row id="frame-limit"><entry><command>Frame-limit</command> &l-r;</entry> <entry><command>:fl</command></entry> - <entry>set the frame-limit: this many frames will be printed - by <command>Backtrace</command> at most.</entry></row> - <row><entry><command>Backtrace</command> [&mode-r; [&l-r;]]</entry> - <entry><command>:bt</command> [&mode-r; [&l-r;]]</entry> - <entry>lists the stack in the given &mode-r;, bottom frame first, top - frame last; at most &l-r; frames are printed.</entry></row> + <entry>set the &frame-limit;: this many frames will be printed + by &backtrace; at most.</entry></row> + <row id="backtrace"><entry>&backtrace; [&stack-mode; [&l-r;]]</entry> + <entry><command>:bt</command> [&stack-mode; [&l-r;]]</entry> + <entry>lists the stack in the given &stack-mode;, bottom frame first, + top frame last; at most &l-r; frames are printed; + calls &show-stack;.</entry></row> </tbody></tgroup></table> <para>If the &cur-frame; is an &eval; or &apply; frame, the @@ -5782,6 +5784,14 @@ and then compiled, back to its interpreted form.</para> </section> +<section id="show-stack"><title>Function &show-stack;</title> +<para>The function &show-stack; is called by the &backtrace; command.</para> +<para>It accepts 3 optional arguments:<orderedlist> +<listitem><simpara>&stack-mode;</simpara></listitem> +<listitem><simpara>&frame-limit;</simpara></listitem> +<listitem><simpara><replaceable>start-frame</replaceable></simpara></listitem> +</orderedlist></para></section> + <section id="documentation"><title>Function &documentation;</title> <para>No on-line documentation is available for the system functions (yet), but see <xref linkend="describe"/>.</para></section> Index: impent.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impent.xml,v retrieving revision 1.384 retrieving revision 1.385 diff -u -d -r1.384 -r1.385 --- impent.xml 18 Oct 2010 21:31:22 -0000 1.384 +++ impent.xml 3 Nov 2010 16:47:18 -0000 1.385 @@ -405,6 +405,9 @@ <!ENTITY set-global-handler '<olink targetdoc="impnotes" targetptr="global-handler"><function>EXT:SET-GLOBAL-HANDLER</function></olink>'> <!ENTITY without-global-handlers '<olink targetdoc="impnotes" targetptr="without-global-handlers"><function>EXT:WITHOUT-GLOBAL-HANDLERS</function></olink>'> <!ENTITY shell '<olink targetdoc="impnotes" targetptr="exec"><function>EXT:SHELL</function></olink>'> +<!ENTITY show-stack '<link linkend="show-stack"><function>EXT:SHOW-STACK</function></link>'> +<!ENTITY frame-limit '<link linkend="frame-limit"><replaceable>frame-limit</replaceable></link>'> +<!ENTITY stack-mode '<link linkend="stack-mode"><replaceable>stack-mode</replaceable></link>'> <!ENTITY so-accept '<link linkend="so-accept"><function>SOCKET:SOCKET-ACCEPT</function></link>'> <!ENTITY so-connect '<link linkend="so-connect"><function>SOCKET:SOCKET-CONNECT</function></link>'> <!ENTITY so-opt '<link linkend="so-opt"><function>SOCKET:SOCKET-OPTIONS</function></link>'> @@ -504,6 +507,7 @@ <!ENTITY canonicalize '<link linkend="canonicalize"><function>EXT:CANONICALIZE</function></link>'> <!ENTITY mod-expt '<link linkend="mod-expt"><function>EXT:MOD-EXPT</function></link>'> <!ENTITY compiled-file-p '<link linkend="compiled-file-p"><function>EXT:COMPILED-FILE-P</function></link>'> +<!ENTITY backtrace '<link linkend="backtrace"><command>backtrace</command></link>'> <!ENTITY help '<olink targetdoc="impnotes" targetptr="debugger-main-deb-step"><command>help</command></olink>'> <!ENTITY debugger '<link linkend="debugger">debugger</link>'> <!ENTITY format-bang '<link linkend="format-bang"><literal>~!</literal></link>'> ------------------------------ Message: 3 Date: Wed, 03 Nov 2010 18:05:57 +0000 From: Sam Steingold <sd...@us...> Subject: clisp/doc impbody.xml,1.612,1.613 To: cli...@li... Message-ID: <E1P...@sf...> Update of /cvsroot/clisp/clisp/doc In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv31195 Modified Files: impbody.xml Log Message: show-stack: add an example Index: impbody.xml =================================================================== RCS file: /cvsroot/clisp/clisp/doc/impbody.xml,v retrieving revision 1.612 retrieving revision 1.613 diff -u -d -r1.612 -r1.613 --- impbody.xml 3 Nov 2010 16:47:18 -0000 1.612 +++ impbody.xml 3 Nov 2010 18:05:53 -0000 1.613 @@ -5786,11 +5786,19 @@ <section id="show-stack"><title>Function &show-stack;</title> <para>The function &show-stack; is called by the &backtrace; command.</para> -<para>It accepts 3 optional arguments:<orderedlist> -<listitem><simpara>&stack-mode;</simpara></listitem> +<para>It prints to &standard-output-var; and accepts 3 optional +arguments:<orderedlist><listitem><simpara>&stack-mode;</simpara></listitem> <listitem><simpara>&frame-limit;</simpara></listitem> <listitem><simpara><replaceable>start-frame</replaceable></simpara></listitem> -</orderedlist></para></section> +</orderedlist></para> +<para>It can used to find out what all the threads are up to: +<programlisting language="lisp"> +(&loop; :with out = &standard-output-var; :for &thr; :in (&list-threads;) :do + (&format; out "===~A===~;" &thr;) + (&thread-interrupt; &thr; :function + (&lambda-m; () (&let; ((&standard-output-var; out)) (&show-stack; 1 3))))) +</programlisting> +</para></section> <section id="documentation"><title>Function &documentation;</title> <para>No on-line documentation is available for the system functions ------------------------------ ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev ------------------------------ _______________________________________________ clisp-cvs mailing list cli...@li... https://lists.sourceforge.net/lists/listinfo/clisp-cvs End of clisp-cvs Digest, Vol 55, Issue 2 **************************************** |
