segmentation fault in sc_core::sc_process_b::semantics

[Dineshkumar]

Hi, 

 

I have a complex design that consists of  multiple static and dynamic (spawned) process. I am getting a segmentation fault in sc_core::sc_process_b::semantics function at run time (probably at time when the method is to be invoked). The back trace is as follows.

 

#0  0x00000000006a3395 in sc_core::sc_process_b::semantics (this=0x1ac81f0) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_process.h:669

#1  0x00000000006a395f in sc_core::sc_method_process::run_process (this=0x1ac81f0) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_method_process.h:300

#2  0x00000000006a4a83 in sc_core::sc_simcontext::crunch (this=0xa2d430, once=false) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:488

#3  0x00000000006a18cc in sc_core::sc_simcontext::simulate (this=0xa2d430, duration=...) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:890

#4  0x00000000006a2e0a in sc_core::sc_start (duration=..., p=sc_core::SC_RUN_TO_TIME) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:1583

#5  0x0000000000436c75 in sc_core::sc_start (duration=1000, unit=sc_core::SC_NS, p=sc_core::SC_RUN_TO_TIME) at <Local Installation Path>/systemc-install_2.3.0/include/sysc/kernel/sc_simcontext.h:118

#6  0x00000000004358b5 in sc_main (argc=3, argv=0xa3cdb0) at mnoc_746_main.cpp:50

#7  0x000000000068d366 in sc_core::sc_elab_and_sim (argc=3, argv=0x7fffffff7fa8) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_main_main.cpp:81

#8  0x000000000068d264 in main (argc=3, argv=0x7fffffff7fa8) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_main.cpp:34

 

Any idea of root cause?  I could not share the design due to its complexity and too many files

Thanks for your help

 

Regards,

Dinesh.

[dakupoto]

Hi, 

 

I have a complex design that consists of  multiple static and dynamic (spawned) process. I am getting a segmentation fault in sc_core::sc_process_b::semantics function at run time (probably at time when the method is to be invoked). The back trace is as follows.

 

#0  0x00000000006a3395 in sc_core::sc_process_b::semantics (this=0x1ac81f0) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_process.h:669

#1  0x00000000006a395f in sc_core::sc_method_process::run_process (this=0x1ac81f0) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_method_process.h:300

#2  0x00000000006a4a83 in sc_core::sc_simcontext::crunch (this=0xa2d430, once=false) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:488

#3  0x00000000006a18cc in sc_core::sc_simcontext::simulate (this=0xa2d430, duration=...) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:890

#4  0x00000000006a2e0a in sc_core::sc_start (duration=..., p=sc_core::SC_RUN_TO_TIME) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_simcontext.cpp:1583

#5  0x0000000000436c75 in sc_core::sc_start (duration=1000, unit=sc_core::SC_NS, p=sc_core::SC_RUN_TO_TIME) at <Local Installation Path>/systemc-install_2.3.0/include/sysc/kernel/sc_simcontext.h:118

#6  0x00000000004358b5 in sc_main (argc=3, argv=0xa3cdb0) at mnoc_746_main.cpp:50

#7  0x000000000068d366 in sc_core::sc_elab_and_sim (argc=3, argv=0x7fffffff7fa8) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_main_main.cpp:81

#8  0x000000000068d264 in main (argc=3, argv=0x7fffffff7fa8) at <Local Installation Path>/systemc-src_2.3.0/src/sysc/kernel/sc_main.cpp:34

 

Any idea of root cause?  I could not share the design due to its complexity and too many files

Thanks for your help

 

Regards,

Dinesh.

 

Hello Sir,

In absence of any source code or a bare-bones example, it is

impossible to provide any meaningful help -- guessing games

are useless. A core dump does not ptovide any information

about where the problem is, UNLESS the error messages are

from a debugger -- have you tried the common ones as gdb,

or for memory leaks - valgrind. I do not know what OS you are

using, but these two tools nowadays are integral components

of any Linux distribution. In addition, you are trying to mix static

and dynamic process, which I am sure you understand iis very

difficult to get right. Maybe you should try a very simple

stripped-sown example, get it to work as per your design

specifications and then scale up -- "divide and conquer". Hope

that helps.

[Dineshkumar]

Hi, Thanks for your suggestion.