Thanks very much! I need exactly this, because I intend to build a CHR editor/debug for eclipse IDE. Then I need for the following .pl p(X,Y) :- trace_call_port(call,_, Y is X*X-1), *(X,X,T), -(T,1,Y), trace_exit_port. calling *eclipse.rpc("p(3,Y)");* in Java to see something like this follow output however in Java console (1) 1 CALL p(3, Y) %> creep (2) 2 CALL Y is 3 * 3 - 1 %> skip (2) 2 EXIT 8 is 3 * 3 - 1 %> creep (1) 1 EXIT p(3, 8) %> creep This is possible? (active the mode *trace* for view execution without tktools but using Java) Best regards... Rafael Oliveira On Tue, Oct 14, 2008 at 11:39 PM, Kish Shen <kisshen_at_cisco.com> wrote: > Rafael Oliveira wrote: > >> hi, >> >> if I want create my user trace filtering the paremeters (call, redo...) or >> add new paremeters for trace, for example, if i want create a better view >> of >> trace, what must i use? tktools? >> >> thanks >> >> Rafael Oliveira >> >> >> >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------- >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win great >> prizes >> Grand prize is a trip for two to an Open Source event anywhere in the >> world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> ECLiPSe-CLP-Users mailing list >> ECLiPSe-CLP-Users_at_lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/eclipse-clp-users >> > > The tracer for tktools has a filtering tool that lets you select conditions > you want the tracer to stop > > The debuggong chapter in the User manual has a section on extending the > debugger, see > > http://87.230.22.228/doc/userman/umsroot081.html > > Note that as the document says, this is not really intended for the end > user -- you don't really want to write additional code just to do debugging. > This is intended for the library writer to produce better view of executing > code for the library. A prime example this will be useful for is lib(ech), > which currently shows only the transformed code, which is not very readable. > > If what you want is to examine your goal more closely, I would suggest > using the inspector tool from the tktool set. This lets you navigate into a > term (e.g. the goal at a debug port) and examine it. > > Cheers, > > Kish > > -- > This e-mail may contain confidential and privileged material for the > sole use of the intended recipient. Any review, use, distribution or > disclosure by others is strictly prohibited. If you are not the intended > recipient (or authorized to receive for the recipient), please contact > the sender by reply e-mail and delete all copies of this message. > Cisco Systems Limited (Company Number: 02558939), is registered in > England and Wales with its registered office at 1 Callaghan Square, > Cardiff, South Glamorgan CF10 5BT. >Received on Wed Oct 15 2008 - 20:04:41 CEST
This archive was generated by hypermail 2.2.0 : Thu Feb 02 2012 - 02:31:58 CET