In case of database server release 2.3 (or above), bug
in the
Database::get_device_attribute_property() and in
Database::get_class_attribute_property() : The size of
the returned DbData object (it's a vector) is not correct.
This generates instabilities (could even be core
dumped) when a process linked with V5 requests
attribute configuration to a device still implementing
Device_2Impl (not passed through Pogo) or create an
AttributeProxy object for an attribute belonging to a
Device_2Impl device.
Will be fixed in Tango 5.1
Workaround : Update device code to inherit from
Device_3Impl (using Pogo)
Logged In: YES
user_id=569547
Fixed in TAngo 5.1