Re: Any Known Problems with IO::Socket and/or IO::Select?

in reply to Any Known Problems with IO::Socket and/or IO::Select?

I would try building a debugging perl (i.e. with Configure option -Doptimize=-g), and make sure you can dump core files (check that ulimit -c is large enough, preferably unlimited).

Then run your server under the debugging perl. When it segfaults and dumps core, open up the core file in gdb (gdb -c core) and do a backtrace (bt) to see where it's crashing.

Until you know where the crash is coming from, you're a bit stuck. (Like others here, I'm inclined to doubt that the problem is with IO::Socket or IO::Select, because those modules are both widely used and well-tested, but it's not impossible.)

Comment on Re: Any Known Problems with IO::Socket and/or IO::Select? Select or Download Code

Replies are listed 'Best First'.
Re^2: Any Known Problems with IO::Socket and/or IO::Select? by liverpole (Monsignor) on Feb 06, 2006 at 13:18 UTC
That's a good suggestion -- my version of Perl is already debugging enabled, so I'll try that next. If I'm able to find anything, I will certainly report my results here. @ARGV=split//,"/:L"; map{print substr crypt($_,ord pop),2,3}qw"PerlyouC READPIPE provides"	[reply]

In Section Seekers of Perl Wisdom