Topic created on: February 14, 2011 16:30 CST by nomnom .

Hey folks, first timer here.

I've got Sulley up and running, and it's doing great. However, every so often the client running the session will stop sending, and I'll discover the server running process monitor has this error :

"PED-RPC> connection to client severed during send()"

Now this seems fairly simple. It's coming from pedrpc.py from these couple of lines of code :

        try:
            self.__client_sock.send(struct.pack("<L", len(data)))
            self.__client_sock.send(data)
        except:
            sys.stderr.write("PED-RPC> connection to client severed during send()\n")
            raise Exception

So, my question is, what is the best way to deal with senario? On the client side performing the fuzzing, if I just 'ctrl+c' the session, it exit out of the current test case, and continue on to the next, and all is fine and dandy. That's on the client's side that is doing the fuzzing though.

What I'm thinking is simply putting a call to  __disconnect - instead of raising an exception. Does this make sense? I don't mind missing a single test case out of every thousand or so (i think?). So hopefully the client side will realize the connection has ended, and just continue to the next one.

Thanks for the input :)