The following bugs in omniORB 4.1.2 have been fixed. Update from Subversion to get the fixes.
|
Summary: |
omniNames service failed if no registry entries present
(bug number 1)
|
Date: |
Mon Feb 18 16:20:50 GMT 2008 |
Description: |
If the omniNames Windows service was set up using an external tool,
meaning it had none of its expected registry entries present,
startup failed.
|
|
Summary: |
Incorrect behaviour handling exceptions on VC++ 7.1
(bug number 2)
|
Date: |
Mon Mar 10 11:42:02 GMT 2008 |
Reported by: |
Werner Mausshardt |
Description: |
A bug in Visual C++ 7.1 meant it generated incorrect exception
handling code, leading to strange errors and crashes if exceptions
occurred in remote calls.
|
|
Summary: |
Incorrect enum name in IR IDL
(bug number 3)
|
Date: |
Thu May 29 14:06:00 BST 2008 |
Description: |
The dk_ValueMember enum member was misnamed dk_Member in ir.idl.
|
|
Summary: |
Failure if openening a connection fails with EAGAIN
(bug number 4)
|
Date: |
Tue Jul 15 11:57:45 BST 2008 |
Reported by: |
Dirk Siebnich |
Description: |
If opening a connection failed with EAGAIN, an incorrect while loop
meant that the connection attempt was not properly retried.
|
|
Summary: |
Crash constructing DynAny containing null TypeCodes
(bug number 5)
|
Date: |
Tue Sep 16 10:21:06 BST 2008 |
Description: |
tk_null was not properly handled, and the resulting exception caused
corruption of DynAny state, leading to a crash.
|
Link: |
http://www.omniorb-support.com/pipermail/omniorb-list/2008-August/029667.html |
|
Summary: |
Failure with long computer name on Windows
(bug number 6)
|
Date: |
Fri Sep 19 16:04:44 BST 2008 |
Reported by: |
Luke Deller |
Description: |
Off-by-one error in name handling.
|
Link: |
http://www.omniorb-support.com/pipermail/omniorb-list/2008-September/029690.html |
|
|