Hi,

I need some help on a crash we have with RFA Lib in C++ on Linux.

We use version 8.2.0L2 of the RFA Libraries to subscribe to OMM feed.

We know the reason of the crash; the dictionary of data was outdated (yes it's bad), and a field type was wrong.

In the outdated dictionary the field was defined as REAL64 but it should be UINT64.

We try to call “getAsString()” on the field (which was containing an UINT64 instead of the expected REAL64) and then it crash.

Here is the call stack (api part only):

Program terminated with signal SIGSEGV, Segmentation fault.

#0 0x00007f3ed67d2dd8 in rwfUI64tofractions () from /home/rfa_app/lib/libRFA_Data.so

[Current thread is 1 (Thread 0x7f3ec9df9700 (LWP 10481))]

(gdb) bt

#0 0x00007f3ed67d2dd8 in rwfUI64tofractions () from /home/rfa_app/lib/libRFA_Data.so

#1 0x00007f3ed67d30d2 in rwfReal64tosOpts () from /home/rfa_app/lib/libRFA_Data.so

#2 0x00007f3ed67cc8a2 in rsslRealToString () from /home/rfa_app/lib/libRFA_Data.so

#3 0x00007f3ed67cf706 in _rsslRealAsString () from /home/rfa_app/lib/libRFA_Data.so

#4 0x00007f3ed67cdd1d in rsslEncodedPrimitiveToString () from /home/rfa_app/lib/libRFA_Data.so

#5 0x00007f3ed66eb9f7 in rfa::data::DataBuffer::getAsString() const () from /home/rfa_app/lib/libRFA_Data.so

On our side everything is in a try/catch trapping everything (…) but since it’s a segmentation fault it doesn’t help.

So, my questions:

Is this a known issue of the lib ?

Is it fix in last version (The release note doesn’t say anything on a crash fix but maybe…)?

If not, is it something that can be fixed in the lib (maybe trigger an exception), or can we check something on the field prior to calling getAsString and so avoid the crash?

We want to avoid application crash in production in case of issue with the field dictionary.

Thanks for help.

Patrick.