This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch 0/6] auto-load: intro
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 6 May 2012 18:13:07 +0200
- Subject: Re: [patch 0/6] auto-load: intro
- References: <20120324183557.GA26662@host2.jankratochvil.net> <CAMe9rOpn3LhrrTveLDoSSu6L0337AOrWfKcWReUBsp3VQ-pQBg@mail.gmail.com>
On Sun, 06 May 2012 18:05:16 +0200, H.J. Lu wrote:
> It may be kind of late. But it is very annoying when using the new
> GDB to debug GCC since .gdbinit from GCC is no longer used by
> default. Any suggestions?
The warning it gives similar to
warning: File "/home/jkratoch/redhat/gdb-clean/gdb/gdb-gdb.gdb" auto-loading has been declined by your `auto-load safe-path' set to "/usr/share/gdb/auto-load".
warning: File "/home/jkratoch/redhat/gdb-clean/gdb/gdb-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "/usr/share/gdb/auto-load".
tries to enforce you to specify proper GDB configure option like
--with-auto-load-safe-path=/usr/share/gdb/auto-load:$HOME/src
or even if you really dislike the security feature and/or really do not face
untrusted binaries use the GDB configure option:
--without-auto-load-safe-path
Assuming your GCC tree is in $HOME/src/somewhere/gcc...
Thanks,
Jan