[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Re: Getting backtraces from services without crash dialog
From:       Austin English <austinenglish () gmail ! com>
Date:       2016-09-20 1:32:26
Message-ID: CACC5Q1e1jtE+=4+JZQkyjR8z8064ka31qijc6d_oi9-3iAbFXA () mail ! gmail ! com
[Download RAW message or body]

On Wed, Sep 7, 2016 at 8:40 PM, Austin English <austinenglish@gmail.com> wrote:
> On Wed, Sep 7, 2016 at 8:18 PM, Vincent Povirk <madewokherd@gmail.com> wrote:
>> I haven't tried this, but my suggestion would be to replace the
>> WriteFile in dbg_outputA with a call to wine_dbg_printf, something
>> like:
>>
>> wine_dbg_printf("%.*s", i, line_buff);
>>
>> On Tue, Sep 6, 2016 at 7:18 PM, Austin English <austinenglish@gmail.com> wrote:
>>> Howdy all,
>>>
>>> I asked this in #winehackers, but got no reply.
>>>
>>> I have a program:
>>>
>>> http://www.cressi.com/software
>>> http://www.cressi.com/easyUp/software/CressiPcInterface_2_0_1_37_Installer.zip
>>>
>>> that installs some device drivers that crash when it is starting up.
>>> If I have the crash dialog enabled, I can save their backtraces. If I
>>> disable it, all I see is something like:
>>> wine: Unhandled page fault on write access to 0x0078d000 at address
>>> 0x7bc55e7f (thread 00a1), starting debugger...
>>>
>>> Is there some way for me to get the backtraces to print to a console
>>> (either of the first wine process or of the later running programs? If
>>> the dialog is enabled, there are several crashes, which makes that
>>> inconvenient.
>>>
>>> Thanks!
>>> --
>>> -Austin
>>> GPG: 14FB D7EA A041 937B
>>>
>>>
>
> Thanks Vincent.
>
> The backtraces were interspersed with fixme's (not unexpected), but
> other than that, worked great, thanks.
>
> --
> -Austin
> GPG: 14FB D7EA A041 937B

FYI, I documented this at https://wiki.winehq.org/Winedbg

Thanks again!

-- 
-Austin
GPG: 14FB D7EA A041 937B



[prev in list] [next in list] [prev in thread] [next in thread]