Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: tom@tromey.com
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix windows-nat.c for -Wnarrowing
Date: Wed, 29 Aug 2018 19:33:00 -0000	[thread overview]
Message-ID: <837ek92cke.fsf@gnu.org> (raw)
In-Reply-To: <838t4p2crb.fsf@gnu.org> (message from Eli Zaretskii on Wed, 29	Aug 2018 22:28:40 +0300)

> Date: Wed, 29 Aug 2018 22:28:40 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> CC: tom@tromey.com, palves@redhat.com, gdb-patches@sourceware.org
> 
> I don't understand: EXCEPTION_ACCESS_VIOLATION is defined like this:
> 
>   #define STATUS_ACCESS_VIOLATION 		      0xC0000005
>   #define EXCEPTION_ACCESS_VIOLATION		      STATUS_ACCESS_VIOLATION
> 
> And you've removed DWORD from the definition of xlate.  So where does
> DWORD come from?

Ah, I see: it's a MinGW64 specific thing.  It defines

   #define STATUS_ACCESS_VIOLATION 		      (DWORD)0xC0000005

So I would suggest to do this:

  static const struct xlate_exception xlate[] =
  {
    {(long)EXCEPTION_ACCESS_VIOLATION, GDB_SIGNAL_SEGV},
    {(long)STATUS_STACK_OVERFLOW, GDB_SIGNAL_SEGV},
    {(long)EXCEPTION_BREAKPOINT, GDB_SIGNAL_TRAP},
    {(long)DBG_CONTROL_C, GDB_SIGNAL_INT},
    {(long)EXCEPTION_SINGLE_STEP, GDB_SIGNAL_TRAP},
    {(long)STATUS_FLOAT_DIVIDE_BY_ZERO, GDB_SIGNAL_FPE},
    {-1L, GDB_SIGNAL_UNKNOWN}
  };


  reply	other threads:[~2018-08-29 19:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 17:43 Tom Tromey
2018-08-29 18:39 ` Pedro Alves
2018-08-29 18:58   ` Tom Tromey
2018-08-29 19:01     ` Tom Tromey
2018-08-29 19:09       ` Pedro Alves
2018-08-29 19:31         ` Tom Tromey
2018-08-29 19:16       ` Eli Zaretskii
2018-08-29 19:22         ` Tom Tromey
2018-08-29 19:29           ` Eli Zaretskii
2018-08-29 19:33             ` Eli Zaretskii [this message]
2018-08-29 19:35               ` Tom Tromey
2018-08-29 19:38                 ` Eli Zaretskii
2018-08-29 19:34             ` Tom Tromey

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=837ek92cke.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    --cc=tom@tromey.com \
    /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