winedbg: newbie question (sorry...)

[Robert Shearman]

Molle Bestefich wrote:

> Hello
>
> Carsten Niehaus (cniehaus at gmx.de) over on wine-users gets a page fault
> when he tries to print with this app:
> http://www.learn-line.nrw.de/angebote/gefahrstoffdb/Gefahrstoffe.zip
>
> He's posted a backtrace:
>
>> fixme:commdlg:PRINTDLG_SetUpPrinterListComboA Can't find '(null)' in 
>> printer list so trying to find default
>> wine: Unhandled page fault on write access to 0x0000002e at address 
>> 0x7f6a2540 (thread 0009), starting debugger...
>> Backtrace:
>> =>1 0x7f6a2540 PRINTDLG_WMCommandA+0x619 in comdlg32 (0x7f6a2540)
>>   2 0x7f6a2fb6 in comdlg32 (+0x32fb6) (0x7f6a2fb6)
>
> [snip!]
>
>> 0x7f6a2540 PRINTDLG_WMCommandA+0x619 in comdlg32: movw  %ax,0x2e(%edx)
>
>
> I'm slightly cli-debugger-clueless, so could one of you guys please
> tell me how to convert this:
>
>  PRINTDLG_WMCommandA+0x619
>
> into a proper line number reference to the source file?


If you don't strip comdlg32 then winedbg will pick up the debug 
information from the .dll.so and give you a filename and line number.

So tell the user to install a build with debug information.

-- 
Rob Shearman