Re: [patch] New set auto-load-local-gdbinit + disable it by default

[Jan Kratochvil <jan.kratochvil@redhat.com>]

On Tue, 17 Jan 2012 17:44:32 +0100, Doug Evans wrote:
> <bite> ???  I don't understand.

I was exaggerating the "(top-gdb)" & co. to be "destructive" but I feel it so.


> I also don't understand the reference to making the debugging session
> completely unusable.

Personally I always feared what is that "(top-gdb)" there and what new
breakpoints it created and why it prints complaints which are not printed
normally etc. etc., I just rather quit and and run normal GDB for GDB.

If I want some special environment (.gdbinit) for GDB-to-GDB I can study the
supplied one and _then_ I can load the supplied one.  For a newbie it is
a needless burden to complicate the debugging of GDB even more.


> The user will be surprised if s/he has been using "Makefile" and not
> noticing that someone slipped in "GNUmakefile".  S/he might see it and
> not even know that it trumps his/her own Makefile.

GNUmakefile vs. Makefile... OK.  But running "make" in untrusted source
directory is never safe as Makefile itself is not trusted.

While I occasionally do run "gdb -nx file core" on untrusted crash tarballs
- supplied by customers.  Now I have to use secured VM for it after Python and
libthread_db.so.1 automatic loading crept in.


Thanks,
Jan