Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

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

by robin (Chaplain)
on Feb 06, 2006 at 12:50 UTC ( #528207=note: print w/ replies, xml ) Need Help??


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"

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://528207]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (7)
As of 2015-07-08 07:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (96 votes), past polls