Changeset 3958 for trunk/doc

Timestamp:

Aug 6, 2000, 1:37:17 PM (25 years ago)

Author:

sandervl

Message:

update

File:

• trunk/doc/ReportingBugs.txt (modified) (2 diffs)

trunk/doc/ReportingBugs.txt

@@ -1 @@
-/* $Id: ReportingBugs.txt,v 1.3 2000-08-01 23:17:55 sandervl Exp $ */
+/* $Id: ReportingBugs.txt,v 1.4 2000-08-06 11:37:17 sandervl Exp $ */
 
 Reporting Odin bugs
@@ -24 +24 @@
 In that case, we'll ask you to mail us the entire file. (zipped)
 So please *do not* send huge logfiles to this list!
+
+Generating useful logfiles
+--------------------------
+To enable logging in the debug build, add the following environment variable:
+        SET WIN32LOG_ENABLED=1
+
+This turns on logging for all debug dlls.
+However, this can result in huge logfiles. To reduce the size, use release
+builds of dlls that are not relevant to the problem you're seeing.
+The general rule is that usually only the logging information generated by
+gdi32, kernel32 and user32 is important.
+Use the release build of gdi32 if the problem you're seeing isn't related
+to painting. (gdi32 generates a *lot* of logging information)
+
+Logging.txt contains information on how to selectively enable/disable logging.
+Doing this requires some knowledge about the layout of the Odin source tree 
+and what each source file does.
+
+
+Useful tips
+-----------
+Crashes are always easy to locate in logfiles (search for 'Exception Information'), 
+but improper behaviour isn't.
+In the system menu (top left button of a window), there's a menu item called
+'Put mark in debug log'. Selecting this item puts the line 'Mark requested 
+by user' in the log. 
+This can be useful i.e. if a window is resized improperly after you click
+on a button. To make it easy for us to locate the right log lines, you
+should select the 'Put mark in debug log' menu item and then click on the
+button that causes the problem.
+
 
 ------------ODIN BUGREPORT------------------