Yes, Signal / Slot works via CINT, so you can set the CINT trace mode with the command prompt ".T". Then you will see the traces of all statements those CINT processes. (In your case it will be Signal /Slot connections). T : turn on/off trace mode for all source The CINT built-in debugger alone with the native debugger can help you also. Hope this helps. Valeri -----Original Message----- From: Joe Robe To: roottalk@pcroot.cern.ch Sent: 3/4/02 1:17 PM Subject: [ROOT] how to debug signal/slot problems Hi, is there any way to debug signal/slot problems ? In my apps they sometimes work and sometimes don't and I do not find the bug after hours. I do not get any error messages, just that the slot is not called. Is there any tool where I can see if a signal has been indeed emitted ?? Are there any known problems with derived classes ?? What happens if I connect a signal/slot in the base class and connect the same signal to a new slot in the derived class ? Joe
This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:44 MET