We have a C++ model that interfaces to our Systemverilog sim environmen through Systemverilog DPI.
Currently, debugging inside the C++ model is a non-interactive process -- after a failure is noted in a logfile, we make a 'bes-guess' as to where it came from, and then add vpi printf() statements to the C++ model, re-compile and re-run.
This is probably more of a general C++ debugging question, but is there a way or tutorial guide on how to attach a gdb process (spwaned from Eclipse IDE) to the ncsim simulator, to give me debug-visibility/controllability into the C++ model?
If you are using "irun", you can simply put "-gdb" on the command line.
irun -gdb -f filelist.f ...
It will bring up gdb, do some setup in the debugger and fire off ncsim. It will set a breakpoint that stops the simulation after all of the shared-libraries (that it knows about) have been loaded, so everything should be there for you to set breakpoints in your model and continue.
In reply to TAM1:
I am new to cadence ncsc_run.
Is there any tutorial example for using gdb with ncsc_run and simvision. Especially from docs in tool installation path.
I want to understand how ncsc_run and gdb interact with each other (like passing arguments using +systemc_args and where those argument goes)