[Click] socket.cc patch

[Mark Huang]

Beyers Cronje wrote:
> You da man Mark :)

Er; not yet. Actually, I was only able to reproduce the hard lock because
click-socket.patch introduced a memory bug. I'm not able to reproduce it with
the fixed version attached (click-socket2.patch), or with a fresh Click checked
out from CVS; I must have had an old binary lying around.

If you ever do manage to reproduce the problem, either with Socket as it is
today, or patched with the attached diff, check to see if it's a memory leak or
something more subtle with the scheduler.

--Mark

-------------- next part --------------
A non-text attachment was scrubbed...
Name: click-socket2.patch
Type: text/x-patch
Size: 24725 bytes
Desc: not available
Url : https://amsterdam.lcs.mit.edu/pipermail/click/attachments/20060621/f437afeb/click-socket2-0001.bin