> Cool. Where is the wine debug log? WINEDEBUG is what you're looking for. It's an environment variable that you set before execution of wine that tells wine what you want to see from the logs. What you want is: WINEDEBUG=+relay,+seh wine nameofprog.exe And that will output the log of the calls made (which can be helpful) and everything that happens with seh. On Sun, 17 Oct 2004 10:40:05 -0700, Mark Knecht <markknecht@xxxxxxxxx> wrote: > On Sun, 17 Oct 2004 13:34:58 -0400, James Hawkins <truiken@xxxxxxxxx> wrote: > > > that's coming from my program? Or is it a message coming from Wine? > > > > In a way it's both. I'ts possible that your program makes use of seh > > to catch exceptions, and then seh is printing debug statements about > > the problem. Another option is that part of wine is causing the > > exception, but I'm not sure if we use seh like that or not. You have > > to read through the debug log and try to find out where the exception > > is coming from. If you could attach the part of the log containing > > the seh stuff and then a couple lines of the log before that, we might > > be able to check it out. > > > > James, > Cool. Where is the wine debug log? Or do I have to run Wine in a > debug mode to get it? I did an 'slocate log | grep wine' but found > nothing of interest so I expect I have to run wine in some special > way? > > If you can point me toward some instructions I'll be happy to post > what you ask for. I'm interested in learnign how to do much more of > this stuff. > > thanks, > Mark > -- James Hawkins _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
