Hello Christoph, Good that you figured this out by yourself. G__process_cmd() does not support all of the debugge commands. Especially, s/step and c/continue commands. In theory, v/view and p/print commands should work fine. I am curious if those command does not work. Anyway, if s/step and c/continue commands are important for you, you somehow need to modify G__input() API to capture input from GUI as I explained in my previous e-mail. Thank you Masasharu Goto >Date: Wed, 7 Mar 2001 04:35:12 -0800 (PST) >From: =?iso-8859-1?q?Christoph=20Bugel?= <cbugel@yahoo.com> >To: roottalk@pcroot.cern.ch >Cc: Masaharu Goto <MXJ02154@nifty.ne.jp> >Subject: Re: CINT debugger interface > >Hi, I am replying to myself, as I found out part of >the answer, and now I have another question :) > >According to CINT ref.txt I can use the function >G__process_cmd(). This function executes cint debugger >interface command. There is a warning: > >CAUTION: This API is only for expert's use. Do not use >this API unless you really understand the detail. > >After compiling something, I got a message at runtime >that I should initialize, using G__init_process_cmd(). >So I did that, and then some thing I tried worked. >(such as G__process_cmd("Class",...)), But some other >things didn't work (such as G__process_cmd("v",...), >probably my fault). Also, after things worked for a >while, suddenly it stopped working at all, and I got >the error "Error: could not create file" for *any* >call to this function, regardless of the parameter. >maybe this is connected to a tmp file or something. > >My question is: is there anything special I should >know about, before using these functions? What I want >to do is to use this API in order to send debugger >commands to cint (such as p/print, s/step, etc) >without using the interactive commandline interface. > >Thanks! >Christoph > > > >> Subject: [ROOT] CINT debugger interface >> From: Christoph Bugel <cbugel@netvision.net.il> >> Date: Mon, 5 Mar 2001 01:47:43 +0200 >> To: roottalk@pcroot.cern.ch >> >> Hi, >> >> I am using cint as an interpreter invoked from >> compiled code, by calling G__init_cint(), followed >> by >> G__loadfile() and/or G__exec_text(). >> >> My question is: how can I use cint's debugger >> interface from within my compiled code. I don't want >> an interactive prompt, because the user will >> interact >> at a higher level (probably a gui..) >> >> would I have to manipulate the stdin from my code >> and >> emulate the user keystrokes, or can I get it working >> with G__pause() and just sending debugger commands >> like for example: G__calc("S") ? >> >> Thanks, >> Christoph > > > >__________________________________________________ >Do You Yahoo!? >Get email at your own domain with Yahoo! Mail. >http://personal.mail.yahoo.com/
This archive was generated by hypermail 2b29 : Fri Jun 08 2001 - 11:51:20 MEST