A_MAP.insert(std::pair<uint16_t, THE_STRUCT_TYPE>(Key, A_STRUCT))
A_MAP[Key] = A_STRUCT;
Both methods work on Visual C++ Express 2012.
Both methods fail on VxWorks at run-time with Signal 11.
However, the following does not crash on VxWorks (but since nothing has been inserted, the pair values will be the (un)initialized values):
std::map<uint16_t, THE_STRUCT_TYPE>::iterator itBegin = A_MAP.begin;
printf("A_MAP.begin = %d\n", itBegin);
I woudl appreciate assistance/guidance from anyone with knowledge of the use of STL maps on VxWorks v6.8.
The two methods described use copy construction. Thsi may be the problem for VxWorks, e.g., it may not support copying user defined types. A third method, emplace(), constructs in place but is only available in "C++ 2011".
FWIW:
typedef THE_STRUCT_TYPE
{
char a_char;
uint16_t an_int_array[20];
char a_char_array[10];
uint16_t an_int;
} THE_STRUCT_TYPE
Any news on the use of the map container in v6.8 ? This is really a straightforward usage.
Some documentation exists regarding compile/link flags to specify the range of STL functionality that's available, and even which compler (Diablo/EDG/VxWorks C++ versus GNU C++) to use. This is an administerred tool, for which I have little control/access, adminned by administrators to whom I have little access, so getting license numbers, C++ compiler usage info, etc., is difficult.
I woudl like to know, though, if this type of failure justifies makign that type of effort.
Also, does v6.9 implement the C++ 2011 Standard, specifically the std::unordered_map container ?
A_MAP[Key] = A_STRUCT;
Both methods work on Visual C++ Express 2012.
Both methods fail on VxWorks at run-time with Signal 11.
However, the following does not crash on VxWorks (but since nothing has been inserted, the pair values will be the (un)initialized values):
std::map<uint16_t, THE_STRUCT_TYPE>::iterator itBegin = A_MAP.begin;
printf("A_MAP.begin = %d\n", itBegin);
I woudl appreciate assistance/guidance from anyone with knowledge of the use of STL maps on VxWorks v6.8.
The two methods described use copy construction. Thsi may be the problem for VxWorks, e.g., it may not support copying user defined types. A third method, emplace(), constructs in place but is only available in "C++ 2011".
FWIW:
typedef THE_STRUCT_TYPE
{
char a_char;
uint16_t an_int_array[20];
char a_char_array[10];
uint16_t an_int;
} THE_STRUCT_TYPE
Any news on the use of the map container in v6.8 ? This is really a straightforward usage.
Some documentation exists regarding compile/link flags to specify the range of STL functionality that's available, and even which compler (Diablo/EDG/VxWorks C++ versus GNU C++) to use. This is an administerred tool, for which I have little control/access, adminned by administrators to whom I have little access, so getting license numbers, C++ compiler usage info, etc., is difficult.
I woudl like to know, though, if this type of failure justifies makign that type of effort.
Also, does v6.9 implement the C++ 2011 Standard, specifically the std::unordered_map container ?