Re: Building today's snapshot of GDB with MinGW

Eli Zaretskii
2020-07-01T15:09:16Z

> Cc: gdb-patches@sourceware.org
> From: Simon Marchi <simon.marchi@polymtl.ca>
> Date: Tue, 30 Jun 2020 18:24:11 -0400
>
> However, some of the warnings you get are not expected:
>
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64 settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32 settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i8086 settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64:intel settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32:intel settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x86-64:nacl settings.
> warning: A handler for the OS ABI "Windows" is not built into this configuration of GDB. Attempting to continue with the default i386:x64-32:nacl settings.
>
> We would not expect GDB to complain for Windows on i386:x86-64.
>
> The first thing I would do is make sure that the function _initialize_amd64_windows_tdep
> gets executed at startup in your GDB. This is the function that registers a handler for
> the tuple (i386:x86-64, Windows).

Thanks, I will take a look there and report what I see.