From: William Morris (wrm_at_innovation-tk.com)
Date: Mon Nov 05 2001 - 09:31:27 GMT
On Fri, Nov 02, 2001 at 03:30:00PM +0000, Mike Ellis wrote: > Hiya! > > >I frequently find that UPS causes my computer to run *very* slowly > >for a period and then to recover for a while (eg when UPS hits a > >breakpoint). This makes the debugger almost unusable on certain > >programs - it appears (although this may be coincidence) to be worst > >on programs that use network sockets. Mike Thanks for suggestion. > Just a wild stab in the dark - are you using "step" to miss out things like > calls to socket(), bind() etc, or are you using "next". No, unfortunately the problem doesn't just appear on stepping, but on any activity (eg just running). I was probably wrong to mention sockets - I don't think the problem is restricted to such programs. An example of the problem: I just started a simple X client under ups. The client is running with no break points. It has no background activity so it is just waiting for X events. Mutt is open partially hiding the debugger and the program under test and also partially hiding my clock (buiciClock). The clock second-hand is advancing in steps of 5-10 seconds (without UPS it is every second). If I push Mutt to the back of the window stack, the clock, UPS and X client windows remain unrefreshed for 5=10 seconds after which they are repainted once (and the clock ticks on by the interval). xload is showing a heavy continuous load implying that UPS is busy doing something. Any help greatfully received. -- William Morris wrm_at_innovation-tk.com
This archive was generated by hypermail 2.1.4 : Wed Feb 13 2002 - 21:51:34 GMT