wine users - Apr 2005 - Help with using the WINEDEBUG variable

Hi users.

I have found the WINEDEBUG variable to be very useful. However, now that my
program starts, using WINEDEBUG=trace,+all or WINEDEBUG=+all creats log
files well over 2.0 GB.

I am trying to find messages like the following:
0009:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x4725f1

(and the few lines above it) to try and figure out what's causing my
Dreamweaver to crash. Originally, DW wouldn't start and I found this in my
log files using WINEDEBUG=+all:
-----------
0009:Ret  ws2_32.gethostbyname() retval=00000000 ret=004725f1
0009:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x4725f1
-----------

This told me that gethostbyname() was supposed to store a value in address
0x4725f1 and did not, causing DW to crash.

I have fixed that problem thanks to help from users on this list, but now it
crashes when I click on "sites" with the same error "Dreamweaver
encountered
a fatal exception. Dreamweaver will now terminate." I can no longer use
WINEDEBUG=+all because of the huge log files.

The man pages state that you can use only WINEDEBUG=<var>,+channel where
<var> is one of err, warn, trace, or nothing, and channel was not defined.
I
know only that you can use +dll, +loaddll, +all. Restricting my logs with
err,warn,or trace messages does not give me what I need, and dlls are not
useful to me here.

I also tried piping the output through "grep" like so:
"WINEDEBUG=+all wine
Dreamweaver.exe | grep RaiseException > debug.log 2>&1" but I got
a 0 byte
file.

Any information on valid settings for WINEDEBUG would be helpful.

Thanks in advance.

On Thu, 28 Apr 2005 09:03:15 -0400, Angela Burrell
wrote:
> -----------
> 0009:Ret  ws2_32.gethostbyname() retval=00000000 ret=004725f1
> 0009:trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x4725f1
> -----------
> 
> This told me that gethostbyname() was supposed to store a value in address
> 0x4725f1 and did not, causing DW to crash.
No, not quite. Retval is what the functions result was. Ret is the code
address that the function was called from. You can normally ignore it but
it's useful for disassembly.
 
> Any information on valid settings for WINEDEBUG would be helpful.
There's a slightly out of date list here:

http://winehq.org/site/docs/wine-user/x1824#AEN1826

thanks -mike

Angela Burrell wrote:
> ...
> Any information on valid settings for WINEDEBUG would be helpful.
> 
If you have not already figured it out, you will find that near the 
beginning of most Wine source files is a line like:

WINE_DEFAULT_DEBUG_CHANNEL(seh);

That means that most of the trace messages in that file will be 
triggered with the "seh" debug channel (or of course "all").