Objects typically call xfer_close() as part of their response to a close() message. If the initiating object has already nullified the xfer interface then this isn't a problem, but it can lead to unexpected behaviour when the initiating object is aiming to reuse the connection and so does not nullify the interface. Fix by always temporarily nullifying the interface during xfer_close() (as was already being done by xfer_vreopen() in order to work around this specific problem). Reported-by: infernix <infernix@infernix.net> Tested-by: infernix <infernix@infernix.net>tags/v0.9.8
|
||
188 | 188 |
|
189 | 189 |
|
190 | 190 |
|
191 |
|
|
192 | 191 |
|
193 | 192 |
|
194 |
|
|
195 | 193 |
|
196 | 194 |
|
197 |
|
|
198 |
|
|
199 |
|
|
200 | 195 |
|
201 | 196 |
|
202 | 197 |
|
|
||
45 | 45 |
|
46 | 46 |
|
47 | 47 |
|
48 |
|
|
48 | 49 |
|
49 | 50 |
|
50 | 51 |
|
51 | 52 |
|
53 |
|
|
52 | 54 |
|
55 |
|
|
53 | 56 |
|
54 | 57 |
|
55 | 58 |
|