Debugging WINE dll...

All development related issues welcome

Moderator: Moderator Team

Post Reply
murphy666
Posts: 7
Joined: Tue Nov 30, 2004 11:15 pm
Location: Montreal, Canada

Debugging WINE dll...

Post by murphy666 » Sun Oct 16, 2005 3:51 am

Hi,

I started playing with the reactos source code (more precisely the explorer source) and done some modification. When I test the new code in Windows XP VS ReactOS, I get different result (control resize problem). My problem seem to come from comctl32.dll which i think is a Wine DLL. My question is how I can debug Wine DLL in ReactOS (Get the output of the TRACE MACRO)?

I got some debug info (Debug output from ntoskrnl and drivers ) when i have tested with VMWARE (SERIAL PORT TO FILE) and REACTOS in debug mode (build with DBG=1 and set /DEBUGPORT=COM1 in the freeldr.ini) but there were no TRACE from comctrl32.dll.

GvG
Posts: 499
Joined: Mon Nov 22, 2004 10:50 pm
Location: The Netherlands

Post by GvG » Sun Oct 16, 2005 9:19 am

TRACE output is normally surpressed, otherwise you'd get a huge log (information overload). You can enable TRACE output for a source file by adding "#define YDEBUG" at the very top of the file.

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests