[Vortex] Debugging / Logging questions
Robert M. Münch
robert.muench at robertmuench.de
Mon Apr 14 14:21:46 CEST 2008
Hi, I'm trying to debug my app and have some problems with the looging.
Below you see a log from WinDBG. I have flagged some lines with ### and
put them on single lines so you can find them faster. vortex_log is my own
log-output handler.
I'm wondering about the garbage characters from the Vortex functions. Than
on the "payload size" and "size" numbers because I think they are to big.
Shouldn't these reflect the number of bytes to transfer / received?
Than the "Expresion ??? have failed..." messages only show garbage for the
expression. At least, it doesn't help me a lot.
Am I doing anything wrong? Robert
0:009> g
vortex_log: peer = (null), domain = vortex-reader
something to read
vortex_log: peer = (null), domain = vortex-frame-factory
### line read from underlying transport: 'ˆþ|¬ýãm'
vortex_log: peer = (null), domain = vortex-frame-factory
from='U' allocating a new frame id=24968688
vortex_log: peer = (null), domain = vortex-frame-factory
### Frame received on channel 24968768, content type=,þ|ÀÊ, transfer
encoding=ƒÄéÃ, payload size=268719456, mime content size=0
vortex_log: peer = (null), domain = vortex-reader
frame received (before all filters)
LLî"L¬ýãmL€GL
vortex_log: peer = (null), domain = vortex-reader
passed initial accept stage
vortex_log: peer = (null), domain = vortex-reader
passed connection existence stage
vortex_log: peer = (null), domain = vortex-reader
about to checking expected message to be received on this channel
vortex_log: peer = (null), domain = vortex-reader
passed message number checking stage
vortex_log: peer = (null), domain = vortex-channel
updating channel receiving status to: msgno=24968908, rpyno=24968860,
seqno=268487107, ansno=268705660..
vortex_log: peer = (null), domain = vortex-reader
passed channel update status due to frame received stage
vortex_log: peer = (null), domain = vortex-channel
SEQ FRAME: not updated, already not consumed half of window advertised:
24968844 < (24968796 / 2)
vortex_log: peer = (null), domain = vortex-reader
passed frame checking stage
vortex_log: peer = (null), domain = vortex-channel
no waiting queue for this message: 24968912
vortex_log: peer = (null), domain = vortex-channel
it seems you didn't define a second level received handler
vortex_log: peer = (null), domain = vortex-connection
increased connection id=24968872 reference to 24968824 by ƒÄé
vortex_log: peer = (null), domain = vortex-thread
### SignalObjectAndWait finished, because:
ØJØJdLØJ\KØJäLØJÜþÀʃÄéÃvortex-thread
vortex_log: peer = (null), domain = vortex-reader
frame delivered on first (profile) level handler channel
vortex_log: peer = (null), domain = vortex-thread
finished vortex_cond_wait from ØJ:34012924
vortex_log: peer = (null), domain = vortex-thread-pool
--> thread from pool processing new job
xp_ans: channel = 11, profile = http://xpeers.net/xp_msg
xp_ans: payload = announce-ft %client/testfile.dat 343580 9
to_rebol_processor: socket created
to_rebol_processor: data send, message = $s
to_rebol_processor: socket closed
vortex_log: peer = (null), domain = vortex-channel
mime headers size calculated for channel 34012804 was: 34012756
vortex_log: peer = (null), domain = vortex-channel
new reply message to sent size (34012824) = msg size (34012776) + mime
size (268487107)
vortex_log: peer = (null), domain = vortex-channel
### sending reply for message 34012848 (size: 34012800)
vortex_log: peer = (null), domain = vortex-channel
updating channel sending status to: msgno=34012804, rpyno=34012756,
seqno=268487107, ansno=268705660..
vortex_log: peer = (null), domain = vortex-sequencer
new message to be sent: msgno 34012816, channel 34012768 (size: 268487107):
vortex-sequencer
vortex_log: peer = (null), domain = vortex-profiles
invocation frame received handler for channel 34012988 finished (first
level: profiles)
vortex_log: peer = (null), domain = vortex-channel
channel=34012960 unref called, ref count status after calling=34012912
xp_request_file: using channel = 9
vortex_log: peer = (null), domain = vortex-connection
decreased connection id=34012940 reference count to 34012892 decreased by
ƒÄé
vortex_log: peer = (null), domain = vortex-frame-factory
deallocating frame id=34012944
vortex_log: peer = (null), domain = vortex-thread-pool
--> thread from pool waiting for jobs
vortex_log: peer = (null), domain = vortex-thread
called vortex_cond_wait from ØJ:34012952
vortex_log: peer = (null), domain =
### Expresion '€$ d d ' have failed, returning: „õ0 at ƒÄéà (:2)
vortex_log: peer = (null), domain =
Expresion 'ˆ$4 4 ' have failed at dõ0 (ƒÄéÃ:268705844)
vortex_log: peer = (null), domain =
Expresion '\TXX' have failed, returning: Dõ0 at ƒÄéà (:2)
vortex_log: peer = (null), domain = vortex-thread
SignalObjectAndWait finished, because:
ØJØJdLØJ\KØJlLØJ°þªÀʃÄéÃvortex-thread
vortex_log: peer = (null), domain = vortex-thread
finished vortex_cond_wait from ØJ:27983568
vortex_log: peer = (null), domain = vortex-sequencer
a new message to be sequenced..
vortex_log: peer = (null), domain = vortex-connection
increased connection id=27983636 reference to 27983588 by ƒÄé
vortex_log: peer = (null), domain = vortex-sequencer
sequence operation: next seq no=27983656 message size=27983608 max seq
no=268487107 step=268760196
vortex_log: peer = (null), domain = vortex-sequencer
the channel is not stalled, continue with sequencing ...
vortex_log: peer = (null), domain = vortex-sequencer
sequencing next message: type=27983648, channel num=27983600,
msgno=268487107, more=268760196, next seq=0 size=268761116 ansno=27983648
vortex_log: peer = (null), domain = vortex-sequencer
frame built, send the frame directly
vortex_log: peer = (null), domain = vortex-sequencer
Sending message, size (27983628) over connection id=27983580, Content:
ƒÄé
vortex_log: peer = (null), domain = vortex-frame-factory
bytes written: 27983600
vortex_log: peer = (null), domain = vortex-frame-factory
write on socket request=27983596 written=27983548
vortex_log: peer = (null), domain = vortex-channel
updating channel sending status to: msgno=27983588, rpyno=27983540,
seqno=268487107, ansno=268705660..
vortex_log: peer = (null), domain = vortex-channel
channel=27983608 unref called, ref count status after calling=27983560
vortex_log: peer = (null), domain = vortex-sequencer
it seems the message was sent completely
vortex_log: peer = (null), domain = vortex-connection
decreased connection id=27983608 reference count to 27983560 decreased by
ƒÄé
vortex_log: peer = (null), domain = vortex-thread
called vortex_cond_wait from ØJ:27983596
More information about the Vortex
mailing list