From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] Allow Windows UNWIND_INFO version 2.
Date: Mon, 09 Dec 2013 10:43:00 -0000 [thread overview]
Message-ID: <20131209104315.GH2527@calimero.vinschen.de> (raw)
In-Reply-To: <20131205034451.GD3175@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]
On Dec 5 07:44, Joel Brobecker wrote:
> > I'd consider merging with the existing loop, so that
> > we print the opcodes when frame debug is enabled.
> >
> > But anyway, this looks fine to me.
>
> Thanks, Pedro. Given Tristan's feedback, I decided to push the patch
> as is. But I remain available to make additional changes, should
> the discussion lead us towards that.
>
> > I clicked on "Did you find this helpful? No" at:
> >
> > http://msdn.microsoft.com/en-us/library/ck9asaa9.aspx
> >
> > and asked for info about v2 and opcode 6. Not holding
> > my breath though.
>
> Ha! Good idea, and I will remember to do that too. It's not much
> effort, and you never know.
I'd suggest to utilize the Microsoft forums at
http://social.msdn.microsoft.com/Forums/en-US/home
My last bugreport got handled pretty quickly, see
http://social.msdn.microsoft.com/Forums/en-US/073d02a6-1181-4694-9e50-d6a05bd80663/
Out of curiosity, will there be a followup for this GDB patch
submission? Handling the v2 opcodes is rather interesting for Cygwin
and Mingw...
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-12-09 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:32 Joel Brobecker
2013-12-03 18:47 ` Pedro Alves
2013-12-03 19:58 ` Corinna Vinschen
2013-12-03 20:04 ` Corinna Vinschen
2013-12-04 8:40 ` Tristan Gingold
2013-12-04 8:43 ` Tristan Gingold
2013-12-05 3:45 ` Joel Brobecker
2013-12-09 10:43 ` Corinna Vinschen [this message]
2013-12-09 11:47 ` Tristan Gingold
2013-12-09 12:11 ` Corinna Vinschen
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=20131209104315.GH2527@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sourceware.org \
/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