tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled b


From: Michael Matz
Subject: Re: [Tinycc-devel] Windows x86_64 BUG, SIGSEV is not correctly handled by installed signal handler.
Date: Tue, 9 Apr 2019 13:07:38 +0000 (UTC)
User-agent: Alpine 2.21 (LSU 202 2017-01-01)

Hi,

On Tue, 9 Apr 2019, Christian Jullien wrote:

> With 64bit version, VisualStudio debugger stops on
> 
> 0x0000000000401087 move byte ptr [rax],cl
> Exception thrown at 0x0000000000401087 in signal.exe: 0xC0000005: Access
> violation writing location 0x0000000000000000.

So, up to here everything is as expected ...

> "Continue", this time, gives
> Unhandled exception at 0x0000000000401087 in signal.exe: 0xC0000005: Access
> violation writing location 0x0000000000000000

... but this should have been transformed into delivering a signal like in 
32bit.  I know that signals are somewhat special on Windows and that it 
supports only a subset of POSIX signals natively, but SEGV is among those 
supported.  Does the example work when compiled by visual studio?  If so, 
what's the difference that matters? :)


Ciao,
Michael.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]