Hello Christoph, I am happy to answer your question. Concerned about debugger interface from GUI, right now, cint does not have good support. However, you could find a way out by looking at src/input.c G__input() function. Basically, all (or at least most) of the debugger interactions are done throught G__input() API. If you make a modification to this function, for example, to intercept input to/from GUI thread, you could make what you want happen. I guess you need to play around with queuing and/or messaging between multiple threads. I am sorry about poor support for this kind of functionality. If you make any progress in this area, please let me know. I am willing to put it into the original as a install option. Thank you Masaharu Goto >Date: Mon, 5 Mar 2001 01:47:43 +0200 >From: Christoph Bugel <cbugel@netvision.net.il> >To: roottalk@pcroot.cern.ch >Subject: [ROOT] CINT debugger interface >User-Agent: Mutt/1.2.5i > >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 > > > >----- End forwarded message ----- > >-- >Org: CERN, European Laboratory for Particle Physics. >Mail: 1211 Geneve 23, Switzerland >E-Mail: Fons.Rademakers@cern.ch Phone: +41 22 7679248 >WWW: http://root.cern.ch/~rdm/ Fax: +41 22 7677910
This archive was generated by hypermail 2b29 : Tue Jan 01 2002 - 17:50:39 MET