On 03/14/12 12:13, deadalnix wrote: > Le 13/03/2012 23:24, Vladimir Panteleev a écrit : >> I think something like this needs to end up in Druntime, at least for >> Linux x86 and x64. > > You are loosing EAX in the process. It's somewhat unavoidable. One way or another, you need to find _some_ threadlocal spot to stick those extra size_t.sizeof bytes, since you mustn't lose data, but the hack works by _overwriting_ the return address.
- Turning a SIGSEGV into a regular function call under Li... FeepingCreature
- Re: Turning a SIGSEGV into a regular function call... deadalnix
- Re: Turning a SIGSEGV into a regular function ... FeepingCreature
- Re: Turning a SIGSEGV into a regular function call... Vladimir Panteleev
- Re: Turning a SIGSEGV into a regular function ... FeepingCreature
- Re: Turning a SIGSEGV into a regular funct... Vladimir Panteleev
- Re: Turning a SIGSEGV into a regular f... deadalnix
- Re: Turning a SIGSEGV into a regu... Vladimir Panteleev
- Re: Turning a SIGSEGV into a ... deadalnix
- Re: Turning a SIGSEGV into a regular function ... deadalnix
- Re: Turning a SIGSEGV into a regular funct... FeepingCreature
- Re: Turning a SIGSEGV into a regular funct... Vladimir Panteleev
- Re: Turning a SIGSEGV into a regular f... deadalnix
- Re: Turning a SIGSEGV into a regu... Vladimir Panteleev
- Re: Turning a SIGSEGV into a ... deadalnix
- Re: Turning a SIGSEGV int... Vladimir Panteleev
- Re: Turning a SIGSEGV int... deadalnix
- Re: Turning a SIGSEGV int... Vladimir Panteleev
- Re: Turning a SIGSEGV int... deadalnix
- Re: Turning a SIGSEGV int... Vladimir Panteleev