Wolf
Illegal operation and shutdown after 1 successful line of copy off the
air of XES.
WOLF_GUI caused an invalid page fault in
module WOLF_GUI.EXE at 017f:0040a429.
Registers:
EAX=c10ad974 CS=017f EIP=0040a429 EFLGS=00010283
EBX=00000064 SS=0187 ESP=0198fef0 EBP=0198ff00
ECX=00000005 DS=0187 ESI=00000008 FS=129f
EDX=c10ad974 ES=0187 EDI=8195d92c GS=0000
Bytes at CS:EIP:
df 04 55 b8 dc 6c 00 d9 5d f4 ff 05 bc dc 8c 00
Stack dump:
00480236 00000064 00000005 004070a9 0198ff4c 00406f87 8195e480 00000ae1
d75e59a5 40e04b33 51757ee3 c1183783 00000000 c0c4f080 c68dbc6e 3fe41a83
Buf usage running 0.4% before crash. After crash buf usage frozen at
89607.7%
Hope this info is helpful.
Jay, W1VD
----- Original Message -----
From: "Wolf DL4YHF" <[email protected]>
To: "RSGB LF Group" <[email protected]>
Sent: Sunday, April 17, 2005 5:43 PM
Subject: LF: Re: WOLF WAV decode
Hi John,
< sorry my direct response to you bounced, so sent again via
reflector. Apologies to the group ! >
Thanks for the info.
I now got a crash when decoding a certain wave-file too, it looks like
some un-initialized thingy somewhere (often a floating-point
variable).
But at least I am now able to trace this issue.
I am still not sure about the output volume - does changing the
"Output
attenuation" parameter (same as -a option) have any effect ?
One of the major differences between WOLF and all the rest is the 8000
Hz sampling rate. This may be not supported by some drivers. I will
add
the option to run WOLF at 11025 Hz too, because this sampling rates
used
to cause less problems with certain soundcard drivers.
Best regards,
Wolf DL4YHF .
| 