Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Christian Biesinger <cbiesinger@google.com>,	gdb-patches@sourceware.org
Cc: Pedro Alves <palves@redhat.com>,	Simon Marchi <simon.marchi@polymtl.ca>
Subject: [review v5] Import the strerror_r-posix module and use it in GDB.
Date: Wed, 13 Nov 2019 03:41:00 -0000	[thread overview]
Message-ID: <20191113034122.CD84D20AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1573068905000.I5cfeb12a5203a4cd94a78581541e6085a68685c3@gnutoolchain-gerrit.osci.io>

Christian Biesinger has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/514
......................................................................


Patch Set 5:

> Patch Set 4: Code-Review+2
> 
> This is OK.  Thanks for doing this.
> 
> With this, do you still see a reason for mingw not using the posix-strerror.c version too?
> 
> I think this code in strerror-override.c ends up being equivalent to the FormatMessage call:
> 
> # if HAVE_WINSOCK2_H
>       /* WSA_INVALID_HANDLE maps to EBADF */
>       /* WSA_NOT_ENOUGH_MEMORY maps to ENOMEM */
>       /* WSA_INVALID_PARAMETER maps to EINVAL */
>     case WSA_OPERATION_ABORTED:
>       return "Overlapped operation aborted";
>     case WSA_IO_INCOMPLETE:
>       return "Overlapped I/O event object not in signaled state";
>     case WSA_IO_PENDING:
> ...
> 
> ... even if the messages may change a little.

Yes, I believe that's correct. I was wondering about pex_run but that takes care to use ENOENT, etc. I will make a patch for that.

Meanwhile I will have to land https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/622 before this patch, or else string.h won't be regenerated correctly, leading to compile errors unless you blow away your build directory...


-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I5cfeb12a5203a4cd94a78581541e6085a68685c3
Gerrit-Change-Number: 514
Gerrit-PatchSet: 5
Gerrit-Owner: Christian Biesinger <cbiesinger@google.com>
Gerrit-Reviewer: Christian Biesinger <cbiesinger@google.com>
Gerrit-Reviewer: Pedro Alves <palves@redhat.com>
Gerrit-CC: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Wed, 13 Nov 2019 03:41:22 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment


  parent reply	other threads:[~2019-11-13  3:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 19:35 [review] " Christian Biesinger (Code Review)
2019-11-06 19:56 ` Simon Marchi (Code Review)
2019-11-06 19:59 ` [review v2] " Christian Biesinger (Code Review)
2019-11-06 20:00 ` Christian Biesinger (Code Review)
2019-11-11 19:49 ` [review v3] " Christian Biesinger (Code Review)
2019-11-11 22:22 ` [review v4] " Christian Biesinger (Code Review)
2019-11-12 13:25 ` Pedro Alves (Code Review)
2019-11-13  3:41 ` Christian Biesinger (Code Review) [this message]
2019-11-15 19:15 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-15 19:16 ` Sourceware to Gerrit sync (Code Review)

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=20191113034122.CD84D20AF6@gnutoolchain-gerrit.osci.io \
    --to=gerrit@gnutoolchain-gerrit.osci.io \
    --cc=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gnutoolchain-gerrit@osci.io \
    --cc=palves@redhat.com \
    --cc=simon.marchi@polymtl.ca \
    /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