You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: