Testing beta 3

[Lubomir I. Ivanov]

On 5 October 2015 at 23:50, Dirk Hohndel <dirk at hohndel.org> wrote:
> On Mon, Oct 05, 2015 at 02:45:04PM +0300, Lubomir I. Ivanov wrote:
>> On 5 October 2015 at 14:30, Steve <stevewilliams at internode.on.net> wrote:
>> >
>> > And the same message box that states:
>> > subsurface.exe has stopped working
>> >
>>
>> could you please:
>>
>> press the "Windows key" + R:
>> type: eventvwr
>>
>> goto WindowsLogs -> Applications.
>>
>> there should be an Error about Subsurface crashing recently.
>>
>> copy / paste the text and send it here to the mailing list.
>
> Faulting application name: subsurface.exe, version: 0.0.0.0, time stamp:
> 0x56114c6e
> Faulting module name: msvcrt.dll, version: 7.0.10240.16384, time stamp:
> 0x559f3e0e
> Exception code: 0xc0000005
> Fault offset: 0x00088fec
> Faulting process id: 0xe18
> Faulting application start time: 0x01d0ffadd569a93f
> Faulting application path: C:\Program Files
> (x86)\Subsurface\subsurface.exe
> Faulting module path: C:\Windows\SYSTEM32\msvcrt.dll
> Report Id: 44baed00-550b-4712-ace1-00da3991e4c4
> Faulting package full name:
> Faulting package-relative application ID:
>
> - why is the version 0.0.0.0 ?

i have no idea.

> - what information does this give me?
>

it says that something is causing a SIGSEGV in the standard C library.
if i can reproduce it without debug symbols i would start setting
breakpoints and disassembling to obtain a meaningful backtrace.
if i have debug symbols tools like GDB makes this easy.

> That's so entirely not helpful, Microsoft...
>

i agree. :-(
mind that my suggestion about the semi-release-debug builds with
external symbols is still viable as you will have debug symbols for
the release builds that reach the users.

lubomir
--