Eric Will
10/5/2008 9:09:00 PM
On Sun, Oct 5, 2008 at 4:44 PM, Yukihiro Matsumoto <matz@ruby-lang.org> wrote:
> Hmm, let's step forward one by one. You have two timers, which one is
> causing the problem? What if wrapping timer callbacks with begin and
> rescue?
I've tried wrapping the start method in timer.rb, wrapping the Timer
callbacks outside of "Timer.new" and inside of "Timer.new" (ie, part
of the callback), and none of these rescue it. When I wrap the call to
ioloop (which is the ENTIRE program, basically) it catches it... which
doesn't really narrow it down much.
I'm trying as I'm writing this, so bare with me for a moment...
wrapping c.read in lib/xmppd.rb catches it... wrapping parse in
Stream#read with it does NOT catch it. So it's somewhere between
Stream#read's call to Stream#parse.
> matz.
I'll keep playing with this, but I don't know that I'm getting very
far... I still think it has something to do with threads.
-- Eric Will