25 Dec
2012
25 Dec
'12
1:09 a.m.
On 09/12/12 11:55, Igor R wrote:
I did both things. The destructor never gets called. The native socket changes from 24 to -1 (which I guess it means it is also wrong). -1 means "invalid descriptor", and this is actually the point where is_open() would return false. But did you spot the moment where it changes to -1? I cannot find what changes it to -1. I put some print statements in boost asio, and I got the following log, which is very strange. The following line appears twice at the beginning when it should appear once, I think.
0x7f1f180010f8 >>>>>>>>>>>> construct socket is now invalid -1