From: Paul Gofman <pgofman@codeweavers.com>
Subject: Re: [PATCH] ntdll: Don't reset rsp to context->Rsp until exception data is copied.
Message-Id: <4c9220ac-b7bd-6bc0-1830-6b714540e3b3@codeweavers.com>
Date: Thu, 2 Jul 2020 12:11:50 +0300
In-Reply-To: <87ftaa5llm.fsf@wine>
References: <20200702080604.544894-1-pgofman@codeweavers.com> <87ftaa5llm.fsf@wine>

On 7/2/20 12:09, Alexandre Julliard wrote:
> Paul Gofman <pgofman@codeweavers.com> writes:
>
>> Context record may be stored on stack below context stack. This
>> happens, e. g., with RtlRaiseException().
> That doesn't seem right, there may be other things on the stack too. Is
> there a reason to switch stack to context->Rsp at all?
>
Exception unwinding does not work otherwise, and that matches stack
layout on Windows: the context and exception record on stack has a fixed
gap after context's Rsp. But it looks we don't need anything else from
the stack besides the context, or am I missing something?