bug with FQ

[Arnaud Legout <Arnaud.Legout@eurecom.fr>]

There is a bug with FQ scheduling that appears only when one does not
trace anything
(using trace-all or trace-nam)
I am using ns2.1b5.

when I run:
set ns [new Simulator]
set f [open out.tr w]
#$ns trace-all $f
set n0 [$ns node]
set n1 [$ns node]
$ns duplex-link $n0 $n1 5Mb 2ms FQ
set udp0 [new Agent/UDP]
$ns attach-agent $n0 $udp0
set cbr0 [new Application/Traffic/CBR]
$cbr0 attach-agent $udp0
set null0 [new Agent/Null]
$ns attach-agent $n1 $null0
$ns connect $udp0 $null0
$ns at 0 "$cbr0 start"
$ns at 10.0 "exit 0"
$ns run



I have got the following error:
ns: _o20 unknown-flow 0 256 0 0: can't read "drpT_": no such variable
    while executing
"$q drop-target $drpT_"
    (procedure "_o15" line 12)
    (FQLink new-flow line 12)
    invoked from within
"$fq_ new-flow $src $dst $fid"
    (procedure "_o20" line 3)
    (Classifier/Hash/Fid/FQ unknown-flow line 3)
    invoked from within
"_o20 unknown-flow 0 256 0 0"

If I uncomment the trace-all line eveythings seems ok (I mean the trace
is reasonable
for FQ scheduling).

Arnaud.
-- 
----------------------------------------------------------------------
Arnaud Legout

Institut Eurecom               	Phone : 00.33.4.93.00.26.61
2229, route des Cretes         	Fax   : 00.33.4.93.00.26.27
BP 193                         	E-mail: Arnaud.Legout@eurecom.fr
06904 Sophia Antipolis cedex    Web   : http://www.eurecom.fr/~legout    
FRANCE                    
----------------------------------------------------------------------