Re: [RP] SMP and ratpoison

[Shawn Betts]

William R Thomas <address@hidden> writes:

> I am not sure how closely the Sourceforge bug tracker is being
> followed for ratpoison, so I figured I would repost here.
> 
> The text if the original bug is available here:
> http://sourceforge.net/tracker/index.php?func=detail&aid=651655&group_id=10306&atid=110306
> 
> But the short synopsis is, with every version of ratpoison I have
> tried, I have been plagued with ratpoison becoming unresponsive and X
> windows needing to be restarted to allow me to do anything related to
> windowing.  The ratpoison maxes out the processor, and any 'ratpoison
> -c's stick around forever without doing anything.
> 
> Using the same version of ratpoison + the same libraries etc at my
> house, ratpoison is as stable as can be.  The only difference I have
> been able to determine is that my work machine is SMP.
> 
> Is anyone running ratpoison on an SMP box with success?  Has anyone
> seen this type of behavior and figured out what is going on?

Hi William,

No the bugs aren't very closely watched..I just don't have time :(. I
will look at it now, though. The best way to get our attention is to
post to the list.

I have never tested rp on SMP machines, so I'm not surprised it's a
bit buggy :).

Is it possible for you to attach a debugger to ratpoison and find out
where ratpoison is dieing? I'm guessing it's getting into some silly
loop and just grinding forever. It could be some X event loop where
ratpoison makes some event, which X sends back to ratpoison which in
turn produces the same event. The only place I can think of this
happening is perhaps in the maximize code...it's possibly the yukkiest
part.

Do you need further instructions on getting a backtrace with GDB?

Thanks,
Shawn