4 Some simple advice on making your bug report more useful (and thus more
5 likely to get answered and fixed):
7 1) Post as much information as possible.
9 This means we need more information than a simple
10 "MS Word crashes whenever I run it. Do you know why?"
11 Include at least the following information:
13 - Version of Wine you're using (run 'wine -v')
14 - Operating system you're using, what distribution (if any), and what
16 - Compiler and version (run 'gcc -v')
17 - Windows version, if installed
18 - Program you're trying to run, its version number, and a URL for
19 where the program can be obtained (if available)
20 - Command line you used to start wine
21 - Any other information you think may be relevant or helpful, such as
22 X server version in case of X problems, libc version etc.
24 2) Re-run the program with the -debugmsg +relay,+snoop option
25 (i.e., 'wine -debugmsg +relay,+snoop sol.exe').
27 If Wine crashes while running your program, it is important that we
28 have this information to have a chance at figuring out what is causing
29 the crash. This can put out quite a lot (several MB) of information,
30 though, so it's best to output it to a file. When the Wine-dbg> prompt
33 To accomplish this, use the following commands:
35 tcsh and other csh-like shells:
37 wine -debugmsg +relay,+snoop [other_options] program_name |& tee filename.out
38 tail -100 filename.out > report_file
40 bash and other sh-like shells:
42 wine -debugmsg +relay,+snoop [other_options] program_name 2>&1 | tee filename.out
43 tail -100 filename.out > report_file
45 'report_file' will now contain the last hundred lines of the debugging
46 output, including the register dump and backtrace, which are the most
47 important pieces of information. Please do not delete this part, even
48 if you don't understand what it means.
50 3) Post your report to the newsgroup comp.emulators.ms-windows.wine
52 In your post, include all of the information from part 1), and insert
53 the text from the output file in part 2). If you do this, your chances
54 of receiving some sort of helpful response should be very good.
56 4) Questions and comments
58 If after reading this document there is something you couldn't figure
59 out, or think could be explained better, or that should have been
60 included, please post to comp.emulators.ms-windows.wine to let us know
61 how this document can be improved.