Darin, I've done what you've said, but still can't figure this out. This is the debug from the time frame I'm testing the function (my comments in parentheses):
-1220467008[8068548]: III AsyncWait [this=87a65e4] -1254163536[828c3b8]: OOO WriteSegments [this=87a6610 count=4096] -1254163536[828c3b8]: OOO appended new segment -1254163536[828c3b8]: OOO rolling back write cursor 0 bytes -1254163536[828c3b8]: OOO advancing write cursor by 54 -1254163536[828c3b8]: OOO CloseWithStatus [this=87a6610 reason=80470002] -1254163536[828c3b8]: PPP nsPipe::OnPipeException [reason=80470002 output-only=1] -1254163536[828c3b8]: nsPipeOutputStream::OnOutputException [this=87a6610 reason=80470002] -1254163536[828c3b8]: OOO CloseWithStatus [this=87a6610 reason=80470002] -1254163536[828c3b8]: PPP nsPipe::OnPipeException [reason=80470002 output-only=1] -1220467008[8068548]: nsInputStreamPump::OnInputStreamReady [this=8875fe8] -1220467008[8068548]: OnStateStart [this=8875fe8] (Pipe calls the streamconv onStartRequest, which calls listener's onStartRequest successfully) -1220467008[8068548]: OnStateTransfer [this=8875fe8] -1220467008[8068548]: Available returned [stream=87a65e4 rv=0 avail=54] (Pump calls stream converters OnDataAvail() function) -1220467008[8068548]: calling OnDataAvailable [offset=0 count=54] (The gzip payload is 54, so this is correct up to this point) -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 -1220467008[8068548]: III ReadSegments [this=87a65e4 count=1] -1220467008[8068548]: III advancing read cursor by 1 (check_header() function probably confirmed by this point it has a correct Gzip header) -1220467008[8068548]: III ReadSegments [this=87a65e4 count=44] -1220467008[8068548]: III advancing read cursor by 44 (remainder of the buffer read, but then what? If everything was good, it would call the listener's onDataAvailable method, but it didn't) -1220467008[8068548]: OnStateStop [this=8875fe8 status=80004005] (Pipe calls the streamconv onStopRequest, which calls listener's onStopRequest successfully) -1220467008[8068548]: III CloseWithStatus [this=87a65e4 reason=80004005] -1220467008[8068548]: PPP nsPipe::OnPipeException [reason=80004005 output-only=0] -1220467008[8068548]: III CloseWithStatus [this=87a65e4 reason=80470002] -1220467008[8068548]: PPP nsPipe::OnPipeException [reason=80470002 output-only=0] On Fri, 05 May 2006 00:18:00 -0700, Darin Fisher wrote: > you might try generating a NSPR log in a debug build: > > set NSPR_LOG_MODULES=nsStreamPump:5,nsPipe:5 > set NSPR_LOG_FILE=log.txt > > run mozilla or firefox, repro the problem, and then exit. inspect the > log and compare to nsInputStreamPump.cpp and nsPipe3.cpp > > -Darin > > > > On 5/4/06, Eric Waters <[EMAIL PROTECTED]> wrote: >> I'm trying to make the following code work. It appears to load the data >> into in inputStream correctly, as the inputStream.available() == >> data.length (54 in this example). However, the compressed data is never >> sent to my listener. Instead, it calls onStartRequest() and then >> onStopRequest() with status NS_ERROR_FAILURE (generic). >> >> Thanks in advance! _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
