Re: Two observations using GDB 13 snapshot

Eli Zaretskii via Gdb-patches
2023-01-07T14:29:10Z

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: gdb-patches@sourceware.org
> Date: Sat, 07 Jan 2023 15:23:35 +0100
>
> On Jan 07 2023, Eli Zaretskii wrote:
>
> > GNU gdb ((MinGW32 GDB)) 13.0.50.20221217-git
> > Copyright (C) 2022 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.
> > Type "show copying" and "show warranty" for details.
> > This GDB was configured as "i686-pc-mingw32".
> > Type "show configuration" for configuration details.
> > For bug reporting instructions, please see:
> > <https://www.gnu.org/software/gdb/bugs/>.
> > Find the GDB manual and other documentation resources online at:
> > <http://www.gnu.org/software/gdb/documentation/>.
> >
> > For help, type "help".
> > Type "apropos word" to search for commands related to "word"...
> > Reading symbols from ./gdb.exe...
>
> Here you should see a warning:
>
> warning: File "[...]/gdb-gdb.gdb" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
>
> Does it help to copy gdb.exe to gdb and use that?

Probably. I did it the other way around: copied gdb-gdb.gdb to the
.libs subdirectory, and now the prompt is the expected (top-gdb).

So the problem is that we are now using libtool, and that causes the
GDB executable to be in a directory different from where gdb-gdb.gdb
is kept.

Joel, should the build procedure copy gdb-gdb.gdb to the .libs
subdirectory, where the GDB executable now lives?

Thanks.