Re: Bad file Descriptor issue in IO::Socket::INET

in reply to Bad file Descriptor issue in IO::Socket::INET

prashantktyagl:

You don't show any code, so it's hard to tell.

Are you properly checking your return values when performing operations that can fail?
Are you using global variables to hold your socket handles, possibly overwriting them with other things in other parts of your code?
Perhaps you're trying to continue to use a socket handle that closed?

When your only tool is a hammer, all problems look like your thumb.

Comment on Re: Bad file Descriptor issue in IO::Socket::INET

Replies are listed 'Best First'.
Re^2: Bad file Descriptor issue in IO::Socket::INET by prashantktyagi (Scribe) on Nov 19, 2012 at 11:31 UTC
Hi..roboticus Thanks for quick reply. I can show the code but it is too long. This script generates service build using perlsvc. It is written in perl. The code I mentioned checks the port checking if this port is active.	[reply]
Re^3: Bad file Descriptor issue in IO::Socket::INET by marto (Cardinal) on Nov 19, 2012 at 11:36 UTC
"I can show the code but it is too long." Create a short script which purely reproduces the problem you are experiencing. How do I post a question effectively?. Earlier: "It was working fine before then I did some changes to it and rebuild this" What have you done to determine if the code change introduced this problem? Basic debugging checklist	[reply]

In Section Seekers of Perl Wisdom