[Bug 3570] ZBrush 2 complains about a debugger
Wine Bugs
wine-bugs at winehq.org
Sun Oct 30 02:07:14 CST 2005
http://bugs.winehq.org/show_bug.cgi?id=3570
------- Additional Comments From saulius.krasuckas at elst.vtu.lt 2005-30-10 02:07 -------
| "trace+reg" gives an output
O dear, I misread this as "gives no output". :-]
I am Sorry.
Yet I think you should try running full version with several debug flag combination.
"warn+all" may give you some unusual warnings.
"+loaddll" or "+module" should show the dlls being loaded.
"+relay,+snoop,+msgbox" should give you some application activity just before it
pops up message box if you cut tail of some thousands of lines of Wine output.
"+file,+reg" should give another view of what app is doing.
"+process" will show any child processes launched (I imagine that may be a
reason of seeing no traces)
"+tid" adding this flag shows you what thread does every trace come from.
Then I'd try these:
"+hook",
"+ntdll",
"+nls"
"+server".
But it's hard to tell without having loaded dll list and without a relay trace.
Of course, it's hard to tell what is wrong at first sight. To find unusualities
you can use command 'diff -u' between the log of demo version and the full one.
Then lines belonging only to demo will be prepended with '-', while ones of
full version will get the '+'.
Also you can read some inspiring docs and find some usefull ideas on debugging
and finding how ZBrush copy protection works:
[1] http://www.winehq.org/site/developer-cheatsheet
[2] http://wiki.winehq.org/DebuggingTutorials
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the wine-bugs
mailing list