Building today's snapshot of GDB with MinGW
Eli Zaretskii
eliz@gnu.org
Thu Jul 2 13:50:13 GMT 2020
> Date: Wed, 01 Jul 2020 18:09:11 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb-patches@sourceware.org, brobecker@adacore.com, tromey@adacore.com
>
> > 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.
I started looking at the code, but then I had a eureka moment. You
mentioned _initialize_amd64_windows_tdep, so I presume you assumed my
build is a 64-bit one? It isn't: it's a 3--bit build, and thus
_initialize_amd64_windows_tdep is not even compiled into the binary.
Given that my build is a 32-bit one, it sounds expected to see
warnings I cited, as they all complain about 64-bit architectures,
right?
Incidentally, I wonder why the gdbarch selftest is trying
architectures that are not supported and not even compiled in. What
is the purpose of doing that?
Thanks.
More information about the Gdb-patches
mailing list