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
Documenting known Valgrind errors for future development work. The main branch, dating back to earlier commits as well, produces many Valgrind errors.
The first set of Valgrind errors are uninitialised value errors related to the SystemC library version 2.3.4. An example of the first three (cleaned up) error messages are as follows:
Use of uninitialised value of size 8
at ________: ??? (in ______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Uninitialised value was created by a stack allocation
at ________: ??? (in ______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Use of uninitialised value of size 8
at ______: sc_cor_qt_wrapper (in ______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Uninitialised value was created by a stack allocation
at ______: ??? (in ______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Use of uninitialised value of size 8
at ______: sc_core::sc_thread_cor_fn(void*) (in ______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Uninitialised value was created by a stack allocation
at ______: ??? (in______/systemc-2.3.4/build/src/libsystemc.so.2.3.4)
Additional errors may be due to unobserved issues in simulator code since they involve RAD-Sim function calls. However, they do not affect program behaviour and may be fixed in the future. Examples include:
1591 errors in context 977 of 1000:
Conditional jump or move depends on uninitialised value(s)
at ______: ??? (in /usr/lib/x86_64-linux-gnu/libgcc_s.so.1)
by ______: ??? (in /usr/lib/x86_64-linux-gnu/libgcc_s.so.1)
by ______: _Unwind_RaiseException (in /usr/lib/x86_64-linux-gnu/libgcc_s.so.1)
by ______: __cxa_throw (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.28)
by ______: sc_core::sc_thread_process::suspend_me() (sc_thread_process.h:244)
by ______: sc_core::sc_thread_process::wait_cycles(int) (sc_thread_process.h:393)
by ______: sc_core::wait(sc_core::sc_simcontext*) (sc_wait.cpp:63)
by ______: sc_core::sc_module::wait() (sc_module.h:178)
by ______: axis_master_adapter::OutputEjection() (axis_master_adapter.cpp:70)
by ______: sc_core::sc_process_b::semantics() (sc_process.h:685)
by ______: sc_core::sc_thread_cor_fn(void*) (sc_thread_process.cpp:117)
by ______: sc_cor_qt_wrapper (sc_cor_qt.cpp:259)
Similar errors exist in the other axis and aximm adapters for both InputEjection() and OutputEjection().
The text was updated successfully, but these errors were encountered:
Documenting known Valgrind errors for future development work. The main branch, dating back to earlier commits as well, produces many Valgrind errors.
The first set of Valgrind errors are uninitialised value errors related to the SystemC library version 2.3.4. An example of the first three (cleaned up) error messages are as follows:
Additional errors may be due to unobserved issues in simulator code since they involve RAD-Sim function calls. However, they do not affect program behaviour and may be fixed in the future. Examples include:
Similar errors exist in the other axis and aximm adapters for both InputEjection() and OutputEjection().
The text was updated successfully, but these errors were encountered: