Re: Bug in giop_recv_buffer_unuse()? BiDir GIOP related?



Hi,

On Wed, 2005-12-14 at 14:05 +0100, Jules Colding wrote:
> I have opened the port on which the communication is happening (tcp/951)
> and enabled BiDir GIOP in the server app. The server answer to the test
> client should therefore happen on port 951 as well.
> 
> I can see in my firewall logs that a request is indeed coming on the
> right port, but the client unconditionally fails in
> giop_recv_buffer_unuse() with memory corruption before receiving any
> answer.

Not entirely true. I got this log from the firewall:

# tcpdump -n -e -ttt -i pflog0
tcpdump: WARNING: pflog0: no IPv4 address assigned
tcpdump: listening on pflog0
Dec 14 13:35:21.564142 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: S 4139262222:4139262222(0) win 5840 <mss 1460,sackOK,timestamp[|tcp]> (DF)
Dec 14 13:35:21.564952 rule 10/0(match): pass out on fxp0: 80.163.83.94.951 > 80.62.76.190.54808: S 3105447711:3105447711(0) ack 4139262223 win 64240 <mss 1460,nop,wscale 0,[|tcp]> (DF)
Dec 14 13:35:21.594544 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: . ack 3105447712 win 1460 <nop,nop,timestamp 4733229[|tcp]> (DF)
Dec 14 13:35:21.596702 rule 10/0(match): pass out on fxp0: 80.163.83.94.951 > 80.62.76.190.54808: . ack 1 win 64240 <nop,nop,timestamp 4275059[|tcp]> (DF)
Dec 14 13:35:21.607406 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: P 0:556(556) ack 1 win 1460 <nop,nop,timestamp 4733229[|tcp]> (DF)
Dec 14 13:35:21.609692 rule 10/0(match): pass out on fxp0: 80.163.83.94.951 > 80.62.76.190.54808: P 1:193(192) ack 557 win 65535 <nop,nop,timestamp 4275060[|tcp]> (DF)
Dec 14 13:35:21.632247 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: . ack 193 win 1728 <nop,nop,timestamp 4733238[|tcp]> (DF)
Dec 14 13:35:21.634311 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: F 556:556(0) ack 193 win 1728 <nop,nop,timestamp 4733239[|tcp]> (DF)
Dec 14 13:35:21.634708 rule 10/0(match): pass out on fxp0: 80.163.83.94.951 > 80.62.76.190.54808: . ack 558 win 65535 <nop,nop,timestamp 4275060[|tcp]> (DF)
Dec 14 13:35:21.634943 rule 10/0(match): pass out on fxp0: 80.163.83.94.951 > 80.62.76.190.54808: F 193:193(0) ack 558 win 65535 <nop,nop,timestamp 4275060[|tcp]> (DF)
Dec 14 13:35:21.713648 rule 10/0(match): pass in on fxp0: 80.62.76.190.54808 > 10.0.3.4.951: . ack 194 win 1728 <nop,nop,timestamp 4733244[|tcp]> (DF)

The test client is 80.62.76.190, the server is 10.0.3.4 and the
communication seems to be happening in a BiDir GIOP conforming way.

So something is coming back and seems to be causing ORBit2 to crash in
iop_recv_buffer_unuse(). Can this answer be the cause of the trouble?

Thanks,
  jules




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]