Spatial quickstart with VCS simulation

[saber cheng]

Hi，Matt!

I have tried for such a long time when i do the VCS Simulation with VCS 2016.06

At the very beginning, i can get the result when i run "bash run.sh args"

But now, i can't get anything except below:

[WARNING]: DELITE_NUM_THREADS undefined, defaulting to 1

Executing with 1 thread(s)

Note-[RT_BS] Larger stack needed

  Note: Bumping stack limit from 8192 to 8194 Kbytes.

Command line: ./verilog/accel.bit.bin

--- Stack trace follows:

Dumping VCS Annotated Stack:

No context available

Error: Received ID does not match sent ID

Assertion (cmd->id == id) failed in ../vcs.sw-resources/FringeContextVCS.h, 279

Top: ../vcs.sw-resources/FringeContextVCS.h:279: void FringeContextVCS::connect(): Assertion `0' failed.

i don't know why, is this a bug with VCS or with SPATIAL-QUICKSTART

[Matt F]

Hi Saber,

I don't know what the problem is here.  The only idea I have at this point is to try poking around with gdb to see if anything pops up.  2016 vcs seems to be the only version I don't have access to. 

Can you try these steps and let me know when things go wrong?:

1. $ bin/spatial <app> && cd gen/<app>
   
2. Add -g to CXXFLAGS in either scripts/vcs.mk or vcs.sw-resources/Makefile (only one should exist, depending on which version of spatial you have)
3. $ make
4. Copy everything in run.sh above the ./Top $@ 2>&1 line and run it in the terminal so that the env is set up correctly
   
5. $ gdb --args ./Top <args>
6. Set breakpoint at the line right before where it crashes for you:
1. gdb) b FringeContextVCS.h:278
   
7. probe sim_pid value:
   
1. gdb) p sim_pid
8. This should print out the pid ### of the accel process that it should have started by this point.  We can connect to it in a second gdb session:
9. (in second window) $ sudo gdb -p ###       (sudo may be necessary)
10. (in second window) continue the accel process
    
1. gdb) c
11. (in first window) keep stepping until it crashes and see if anything printed in either window helps us understand what's going on
1. gdb) n
2. <enter> <enter> <enter> ...

Hopefully we can learn something here and get closer to solving the problem.

Thanks

[saber cheng]

Hi Matt！

Thanks for you patience!

I have found that this problem was solved when i use VCS 2014.03. 

So I think maybe this problem is caused because of that VCS2016.06 is an unstable version of VCS. 

Maybe 2014.03 is better

Thank u again!

[saber cheng]

i have tried what you said, but there seems no symbol "sim_pid" in that context.