qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 2/2] util/oslib-win32: Improve error report by calling error_


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH 2/2] util/oslib-win32: Improve error report by calling error_setg_win32()
Date: Thu, 27 Feb 2020 16:35:22 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

On 2/27/20 3:42 PM, Markus Armbruster wrote:
Philippe Mathieu-Daudé <address@hidden> writes:

Use error_setg_win32() which adds a hint similar to strerror(errno)).

Signed-off-by: Philippe Mathieu-Daudé <address@hidden>
---
  util/oslib-win32.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/util/oslib-win32.c b/util/oslib-win32.c
index e9b14ab178..d2fca1808d 100644
--- a/util/oslib-win32.c
+++ b/util/oslib-win32.c
@@ -46,7 +46,8 @@
  void *qemu_oom_check(void *ptr)
  {
      if (ptr == NULL) {
-        fprintf(stderr, "Failed to allocate memory: %lu\n", GetLastError());
+        g_autofree gchar *emsg = g_win32_error_message(GetLastError());

Since we're on a path to abort(), I wouldn't bother with g_autofree.\

This is in case other developers copy that elsewhere.


+        fprintf(stderr, "Failed to allocate memory: %s\n", emsg);

Any particular reason not to use error_report()?

Pre-existing call, but I can change.


          abort();
      }
      return ptr;





reply via email to

[Prev in Thread] Current Thread [Next in Thread]