Hello;
I had a core dump with Ruby 1.6.7 (built from the RPMs at Caliban.org) and
posted it at:
http://www.soup-kitchen.net/bt.txt
My program evidently received a SIGPIPE for reading/writing from a
one-ended pipe, but I assumed that my program would be insulated from this
by IO.popen throwing an EOFException which I have a rescue clause for, and
this worked 99.9% of the time. The code is a fairly simple class which
wraps the execution of a recursive wget process and returns URLs found for
consumption by a matcher. It’s fairly short and posted at:
http://www.soup-kitchen.net/fetch_wget.rb
This class was instantiated many times on many URLs and ran for several
hours before my logs showed a Ruby segfault-- is this a problem with my
code not catching SIGPIPE (which as far as I can tell, is meant to be
ignored in signal.c) or should Ruby have just returned me an EOFError?
cheers,
···
–
Matthew