If you allocate an array with an abstract class, the Memory Manager will allocate the memory like this:
address = calloc( (size_t)n_elems, (size_t)size
(Line 146 in MemoryManager_declare_var.cpp)
The memory is then returned to the caller uninitialized. That is all fine. The issue present itself when someone tries to access uninitialized elements of the array through the trick variable server.
For example, in EventManager::add_to_active_events(Trick::Event * in_event) if the number of active events is 1 trick will allocate an initial array with active_events = (Trick::Event **)TMM_declare_var_s("Trick::Event* [100]");. The Event Manager then assigns the new event to the correct index and returns. If the event is store at index 1, and you try to access the 'name' variable in Trick::Event at index 2 - the sim crashes (segfault).
Line 327 in VariableReference.cpp
// handle c++ string and char*
if ( _trick_type == TRICK_STRING ) {
if (_address == NULL) {
_size = 0 ;
} else {
_size = strlen((char*)_address) + 1 ; <----Crash happens here
}
}
Possible solution:
I haven't tested this extensively, but here's an excerpt from the add_to_active_events function:
if (num_active_events == 1) {
active_events = (Trick::Event **)TMM_declare_var_s("Trick::Event* [100]");
num_allocated = 100 ;
} else if ( num_active_events >= num_allocated ) {
num_allocated += 100 ;
active_events = (Trick::Event **)TMM_resize_array_1d_a(active_events, num_allocated);
for ( unsigned int ii = num_active_events ; ii < num_allocated ; ii++ ) {
active_events[ii] = NULL ;
}
}
Setting uninitialized memory to null outside of the if statements seems to fix the crash.
if (num_active_events == 1) {
active_events = (Trick::Event **)TMM_declare_var_s("Trick::Event* [100]");
num_allocated = 100 ;
} else if ( num_active_events >= num_allocated ) {
num_allocated += 100 ;
active_events = (Trick::Event **)TMM_resize_array_1d_a(active_events, num_allocated);
}
for ( unsigned int ii = num_active_events ; ii < num_allocated ; ii++ ) {
active_events[ii] = NULL ;
}
I don't know if this is the "right" solution, but thought I'd include it as it at least stops the crash from happening.
Fun and interesting behaviors
Crash only happens with std::string, other types resolve to their interpretation of whatever happens to be in their uninitialized memory.
Crash does not happen if num_active_events == 0 (so no memory allocated for this array by the TMM)
After the crash, if you restart the sim and try to look at the Trick Event names again...it works. No crash.
Make clean and try again - crash.
Steps to reproduce:
Add the following event to RUN_test/input.py in SIM_cannon_numeric
Open Trick TV and access trick_em.em.active_events[0][0][0][5]
The last one is a little strange as well. Sometimes it works. From some experimenting, if the garbage in memory happens to translate to an empty string everything works okay. But if it doesn't, then the segmentation fault occurs.
If you allocate an array with an abstract class, the Memory Manager will allocate the memory like this:
address = calloc( (size_t)n_elems, (size_t)size
(Line 146 in MemoryManager_declare_var.cpp)The memory is then returned to the caller uninitialized. That is all fine. The issue present itself when someone tries to access uninitialized elements of the array through the trick variable server.
For example, in
EventManager::add_to_active_events(Trick::Event * in_event)
if the number of active events is 1 trick will allocate an initial array withactive_events = (Trick::Event **)TMM_declare_var_s("Trick::Event* [100]");
. The Event Manager then assigns the new event to the correct index and returns. If the event is store at index 1, and you try to access the 'name' variable in Trick::Event at index 2 - the sim crashes (segfault).Line 327 in VariableReference.cpp
Possible solution:
I haven't tested this extensively, but here's an excerpt from the add_to_active_events function:
Setting uninitialized memory to null outside of the if statements seems to fix the crash.
I don't know if this is the "right" solution, but thought I'd include it as it at least stops the crash from happening.
Fun and interesting behaviors
Steps to reproduce:
The last one is a little strange as well. Sometimes it works. From some experimenting, if the garbage in memory happens to translate to an empty string everything works okay. But if it doesn't, then the segmentation fault occurs.