From: Kris Hagel (hagel@comp.tamu.edu)
Date: Wed Nov 13 2002 - 18:43:11 EST
Hello, I completed (I think) the migration to signal/slot in the online monitor software. This was necessitated by the fact that some of the routines still using the old message sending methods were not compiling after rootcint because of new "features" (I guess) of the 3.04 compiler on the piis. Whatever the reason, the signal/slot is a cleaner way to do business. These modifications are now checked in to the repository There is one caveat. I (or the 3.04 compiler; or root 3.03.09) have manufactured a seg fault when a popup canvas is used by double clicking on a monitor pad. Everything in my tests appears to continue working after the seg fault, but I have the general idea that all seg faults are bad seg faults. I did not manage to locate the problem and rationalized that not many people in brahms besides me use that feature anyway, so I went ahead and committed in the code. But a question to experts (Christian I guess, but anyone else if they know). How do I find where a seg fault happens? I tried with gdb and it says it is in InnerLoop and as far as I can tell it continues there after handling the signal (UNIX signal) It makes me miss VMS again as I remember "back in the good old days" when a program crashed and the computer told you exactly where it crashed and why. Who can help me? I spent a few hours coverting to signal/slot and 2 1/2 days chasing this stupid seg fault and in the end have nothing to show for it. Regards Kris
This archive was generated by hypermail 2.1.5 : Wed Nov 13 2002 - 18:44:31 EST