Experimental Physics and
Industrial Control System

Hello Stefen,

I found _ZNSt9exceptionD2E (or demangled std::exception::~exception) in libstdc++.a in vxWorks 6.2, 6.3, 6.4, 6.6 and 6.7 (all vxWorks 6 I have). So If you include full C++ support in vxWorks, you should have it.

__gxx_personality_v0 is also in libstdc++.a but only in vxWorks 6.7. VxWorks 6.2 - 6.6 have __gxx_personality_sj0.

So If you have vxWorks 6.7 (or maybe higher) with C++ included, you should have the symbols.

Dirk

On 03.06.2016 15:41, Dirk Zimoch wrote:

Hi Stefen,

That basically says that your app1 makes use use of
std::exception::~exception and __gxx_personality_ but they are neither
defined in your code nor already loaded in in the system.

This is vxWorks, right?

Do you have full C++ support included in your vxWorks?

Dirk


On 03.06.2016 15:28, Stefen Paul wrote:

Hello all,

While running EPICS startup script st.cmd on vxWorks for an app that was
made successfully, I am getting following error :

/ld 0,0, "app1.munch"/
/
/
/Warning: module 0x23da5d0 holds reference to undefined symbol
_ZNSt9exceptionD2E/
/v./
/Warning: module 0x23da5d0 holds reference to undefined symbol
__gxx_personality_/
/v0./
/ld(): module contains undefined symbol(s) and may be unusable./
/value = 0 = 0x0/
/
/
/Done executing startup script
'C:\EPICS\base\app1\iocBoot\iocapp1\st.cmd'/


Any clues what might me wrong ?

Thanks,
Stefen.