public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kirill Müller" <krlmlr+gcc@mailbox.org>
To: "Martin Storsjö" <martin@martin.st>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: Patch for 96948
Date: Tue, 8 Sep 2020 17:50:37 +0200	[thread overview]
Message-ID: <9ce86db7-1cf8-417f-6230-d4031e26020a@mailbox.org> (raw)
In-Reply-To: <alpine.DEB.2.23.453.2009081827110.12587@cone.martin.st>

Hi


Thanks for the explanation, this makes sense now.

I haven't actually tested if the cfa value (ms_context.Rsp) is valid, I 
also see no reason why it shouldn't be.

What does it take for your patch to be accepted? What's the minimum gcc 
version where it will be available?


Best regards

Kirill


On 08.09.20 17:34, Martin Storsjö wrote:
> Hi,
>
> On Tue, 8 Sep 2020, Kirill Müller wrote:
>
>> Thanks for the heads up. The coincidence is funny -- a file that 
>> hasn't been touched for years.
>
> I think we both may originally be triggered from the same guy asking 
> around in different places about implementations of _Unwind_Backtrace 
> for windows, actually.
>
>> I do believe that we need the logic around the `first` flag for 
>> consistency with the other unwind-*.c implementations.
>
> Yes, if you store ms_context.Rip/Rsp before the RtlVirtualUnwind step 
> - but my patch stores them afterwards; after RtlVirtualUnwind, before 
> calling the callback.
>
> The result should be the same, except if using the first flag 
> approach, I believe you're missing the last frame that is printed if 
> using my patch.
>
> // Martin

  reply	other threads:[~2020-09-08 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-07  6:12 Kirill Müller
2020-09-08 12:08 ` Martin Storsjö
2020-09-08 13:29   ` Kirill Müller
2020-09-08 15:34     ` Martin Storsjö
2020-09-08 15:50       ` Kirill Müller [this message]
2020-09-08 19:34         ` Martin Storsjö
2020-11-06 16:42       ` Jeff Law
2020-11-06 20:53         ` Martin Storsjö

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ce86db7-1cf8-417f-6230-d4031e26020a@mailbox.org \
    --to=krlmlr+gcc@mailbox.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=martin@martin.st \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).