Re: trouble debugging

[James Hawkins]

I have just run the program with WINEDEBUG=trace+shell and i will
attach the results to this message.  The last function to be called
before the crash is PathCompactPathW.  I'm not sure whether this is
the cause of the crash or not, but I put some test code (from msdn)
into the path section of the shlwapi test suite.  Here are the
results:

MSDN:
The un-truncated path is                C:\path1\path2\sample.txt
The truncated path at 125 pixels is :   C:\path1...\sample.txt
The truncated path at 120 pixels is :   C:\pat...\sample.txt
The truncated path at 110 pixels is :   C:\p...\sample.txt
The truncated path at  25 pixels is :   ...\sample.txt

WINE:The un-truncated path is                C:\path1\path2\sample.txt
The truncated path at 125 pixels is :   C:\path1\path2\sample.txt
The truncated path at 120 pixels is :   C:\path1\path2\sample.txt
The truncated path at 110 pixels is :   C:\path1\path2\sample.txt
The truncated path at  25 pixels is :   C:\path1\path2\sample.txt

Im sure this isnt a very vital function, but I thought I would bring
it to the attention of the developers.

On Sun, 29 Aug 2004 23:41:11 -0400, James Hawkins  wrote:
> Hi,
>
> I'm having a real tough time debugging a program im trying to get to
> run called KLConfigWizard.exe.  I had a problem earlier that was fixed
> by a tip from Rob.  After trying a bunch of different native dll's
> that this program uses, I located the culprit dll (which is about as
> much as I seem to be able to do.)  If I use native shlwapi then the
> crash doesnt happen.  When i'm not using native shlwapi, the output I
> get is:
>
> [truiken@cmu-127081 Kazaa Lite K++]$ wine KLConfigWizard.exe
> Please use the registry key HKEY_CURRENT_CONFIG\Sotfware\Fonts\LogPixels
> to set the screen resolution and remove the "Resolution" entry in the
> config file
> fixme:commctrl:InitCommonControlsEx Unknown class! dwICC=0x4000
> wine: Unhandled exception (thread 0009), starting debugger...
> fixme:console:SetConsoleCtrlHandler (0x405fbab0,1) - no error checking
> or testing yet
> WineDbg starting on pid 0x8
> Unhandled exception: page fault on read access to 0x00000000 in 32-bit
> code (0x00000000).
> In 32 bit mode.
> 0x00000000: addb        %al,0x0(%eax)
> Wine-dbg>bt
> Backtrace:
> =>1 0x00000000 (0x00000000)
> Wine-dbg>q
> WineDbg terminated on pid 0x8
>
> I do have the log of WINEDEBUG=trace+all, but the log file is ~243mb?
> I tried scanning through it looking for anything that would give me a
> clue, but it was hard to tell where any error was.  It also doesnt
> help that the backtrace doesnt contain much of anything.  Any ideas?
>
> --
> James Hawkins