Segmentation fault after running vectore based for

Question

can someone please help me trace this error, i'm using vector based forwarding protocol tcl example on 400 nodes and i got this error

UWSink (id:0): I get the packet data no.0 from 378 
SK 0: Num_Recv 412, InterArrival 0.298128
UWSink (id:0): I get the packet data no.11 from 262 
SK 0: Num_Recv 413, InterArrival 0.057902
UWSink (id:0): I get the packet data no.4 from 79 
SK 0: Num_Recv 414, InterArrival 0.368108
UWSink (id:0): I get the packet data no.10 from 79 
SK 0: Num_Recv 415, InterArrival 0.741583
UWSink (id:0): I get the packet data no.4 from 262 
SK 0: Num_Recv 416, InterArrival 0.216878

Program received signal SIGSEGV, Segmentation fault.
0x000000000060871c in TclRegisterLiteral ()

Answer 1

Also ref. your other AquaSim VBF thread, with the most of a simulation file : VBFP doesnt work probably in aqua-sim

... node 4 - 398 are missing. I filled in some node settings, 4 - 85 by a random external file : source 82-nodePositions . I will suggest that you upload the complete simulation file.tcl to e.g. Dropbox, and post a shared link.

Your errors : Old ns2 code like AquaSim can crash with a late glibc / libc6, e.g. Ubuntu 17.xx .

I made the tests with three 'Linux OS' : PCLinuxOS 2017 - 64, Ubuntu 16.04 - amd64, CentOS 6.9 - i386.

Example result, CentOS 6.9 - 32 :

$ ns-aqua-el6 A.Moh-VBF-n400.tcl

the file name is test.data
the sending interval is 10.0
num_nodes is set 401
Width=100
INITIALIZE THE LIST xListHead
Node 400 is sending first!!
starting Simulation...
GOD: the old file name istest.data
GOD: the new file name istest.data
SINK 0 : terminates (send 0, recv 0, cum_delay 0.000000)
god: the energy consumped is 16681.600000
NS EXISTING...

The trace file test.tr is OK. 92.4 .. 96.8 MB. The nam trace test.nam has no "trace lines" : Indicates that some nam settings are missing in the simulation file.tcl . Or caused by my random node settings.

The complete results https://www.dropbox.com/s/fov2r82s88rfhaq/A.Moh-Nov12-result2.tar.gz?dl=0

---

EDIT : Ref. your comment #2 : Got your new example, "VBF 401 nodes". Tested with PCLinuxOS 2017, CentOS 7.4, Ubuntu 16.04, CentOS 6.9 - 64, and the 32bits CentOS 6.9 → The two usable results can be downloaded from https://www.dropbox.com/s/nl6pnyz3cdklu5g/VBF_example_5-n401-result.tar.gz?dl=0