[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NS 2.1b3 / nam-trace error?



Hi,

I'd like some help regarding the following.

Using NS v. 2.1b3 with SUN's MIP extensions, the following error-message
appears when running ns
with ../tcl/ex/nam-example.tcl 


ns: _o3 run-mcast: invalid command name "0"
    while executing
"[$link set ifacein_] set intf_label_"
    (procedure "_o30" line 3)
    (Node get-oif line 3)
    invoked from within
"$self get-oif $link"
    (procedure "_o30" line 5)
    (Node init-outLink line 5)
    invoked from within
"$node init-outLink"
    (procedure "_o3" line 5)
    (Simulator run-mcast line 5)
    invoked from within
"_o3 run-mcast"

This error doesn't appear when version 2.1b4 (all-in-one) is used.

A similar error occurs when using some test-files with the -namtr <filename>
flag attached, such as mip-test.tcl. (Thierry Ernst reported this too
earlier on.)
The error now is (sorry for the big list):

(_o76 cmd line 1)
    invoked from within
"_o76 cmd attach-nam file4"
    invoked from within
"catch "$self cmd $args" ret"
    (procedure "_o76" line 2)
    (SplitObject unknown line 2)
    invoked from within
"$drpT_ attach-nam $namtrfd"
    (procedure "_o63" line 15)
    (Link/LanDuplex trace line 15)
    invoked from within
"$link_([$n1 id]:[$n2 id]) trace $self $file"
    (procedure "_o3" line 7)
    (Simulator trace-queue line 7)
    invoked from within
"$ns_ trace-queue $src $dst"
    (procedure "_o51" line 14)
    (LanLink attachLL line 14)
    invoked from within
"$self attachLL $src $dst"
    (procedure "_o51" line 28)
    (LanLink addNode line 28)
    invoked from within
"$lan addNode $nodelist $bw $delay"
    (procedure "_o3" line 3)
    (Simulator newLan line 3)
    invoked from within
"$ns newLan "$node(g) $node(ha) $node(fa)" $opt(bw)  $opt(delay) -llType
$opt(ll) -ifqType $opt(ifq)  -macType $opt(mac) -chanType $opt(chan)"
    (procedure "create-topology" line 16)
    invoked from within
"create-topology"
    (file "mip-test.tcl" line 163)


Not using the nam-trace option doesn't give an error.

Is this error because of:

- an error in NS v 2.1b3 (already patched the 'segmentation fault' from the
bug-page)
- an error in NS v 2.1b3 as it comes with the Perkins Mobile IP
distribution?
- myself since I just started using NS and I'm doing something incredibly
stupid.

Please help, Sjoerd Janssen