[prev in list] [next in list] [prev in thread] [next in thread]
List: omniorb-list
Subject: Re: [omniORB] Bug in RECOVER_FORWARD
From: Duncan Grisby <duncan () grisby ! org>
Date: 2008-12-12 17:45:20
Message-ID: 28402.1229103920 () grisby ! org
[Download RAW message or body]
On Friday 12 December, Serguei Kolos wrote:
> I have an impression that a bug has been introduced in the omniORB 4.1.3
> to the handling of the exceptions in case of using reference
> forwarding.
[...]
> The issue is that in the line 790 it is used inside the catch(const
> giopStream::CommFailure& ex) block and as a consequence if a transient
> exception handler returns 0 the giopStream::CommFailure exception is
> propagated to the user space which must never happen.
Yes, it is a bug.
> What is the best way of solving this issue?
Update to the latest CVS snapshot. The bug is already fixed there.
Cheers,
Duncan.
--
-- Duncan Grisby --
-- duncan@grisby.org --
-- http://www.grisby.org --
_______________________________________________
omniORB-list mailing list
omniORB-list@omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic