Re: simultaneous close

Hmmmm...  well that's a bad bug.

Simultaneous from both ends in same channel?

-bill


On Fri, Feb 13, 2004 at 11:40:31AM -0800, Lei Zhang wrote:
> Knowing that beepcore-c is dead, still it's worthwhile reporting this:
> 
> beepcore-c is not able to handle simultaneous channel close.  I see the 
> following call sequences:
> 
>   listener                   initiator
>  
>   close_indication local       close_indication local
>   close_indication remote      close_indication remote
> 
> Neither side gets to the close_confirmation stage.  After waiting a 
> while, kill one peer, the other peer core dumps saying 'assertion 
> "wrap->iostate != 0" failed' in bp_notify.c.
> 
> well, well...
> 
> 
> 
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Beepcore-c-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/beepcore-c-users


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click