I got around this by doing queue.Peek() and then queue.Dequeue(). It won't corrupt the queue.
I will fill a bug report if it isn't already.
Pablo
On Fri, 2002-11-08 at 17:16, Erik C wrote:
http://launch.yahoo.com/u2Ok please help me figure out if my code is bad(most likely the case)...or if this is a bug in the Queue class. It looks like the Queue fills up with 20 objects and then as I dequeue them suddenly the value objects changes after I've dequeued 16 of them?!?! The following debug output was made from the attached code(the code is an attempt of making a port scanner) thanks in advance, -Erik- University of Florida my compile line:: mcs -checked -o Scanner.exe -t:exe Scanner.cs my run line:: mono Scanner.exe -p 1-20 127.0.0.1 snip of output:: Just dequeued emptyQ=False targetQ.COunt=5 port=15 ip=127.0.0.1 Q size=5 This is the Queue now: Port=16 IP=127.0.0.1 isOpen=False Port=17 IP=127.0.0.1 isOpen=False Port=18 IP=127.0.0.1 isOpen=False Port=19 IP=127.0.0.1 isOpen=False Port=20 IP=127.0.0.1 isOpen=False Just dequeued emptyQ=False targetQ.COunt=4 port=16 ip=127.0.0.1 Q size=4 This is the Queue now: Port=1 IP=127.0.0.1 isOpen=False Port=2 IP=127.0.0.1 isOpen=False Port=3 IP=127.0.0.1 isOpen=False Port=4 IP=127.0.0.1 isOpen=False Just dequeued emptyQ=False targetQ.COunt=3 port=1 ip=127.0.0.1 Q size=3 This is the Queue now: Port=2 IP=127.0.0.1 isOpen=False Port=3 IP=127.0.0.1 isOpen=False Port=4 IP=127.0.0.1 isOpen=False __________________________________________________ Do you Yahoo!? U2 on LAUNCH - Exclusive greatest hits videos
