Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] New set auto-load-local-gdbinit + disable it by default
Date: Tue, 17 Jan 2012 17:55:00 -0000	[thread overview]
Message-ID: <20120117174839.GA8459@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22S51Er8=Bdirwbj1h=dn0awZjrfuJWXkX8Fdd3tORKE-g@mail.gmail.com>

On Tue, 17 Jan 2012 18:26:49 +0100, Doug Evans wrote:
> I, OTOH, like the (top-gdb) prompt.

I think you and me can very easily do whatever we like with GDB.  I care more
about both newbie users of GDB and also about newcomers to GDB development.


> One could argue the converse too ... Having to manually request
> whatever goodies the developers find useful adds a needless burden.
> Why can't gdb just auto-adjust itself for debugging the program at
> hand?

Because it is then different than normal GDB.

It is difficult to argue myself but IMO in a survey between GDB newbies they
find easier if GDB behaves always the same than if it behaves differently
according to which program you load into it.


> There is the path that gdb searches for libthread_db, maybe you meant
> to refer to that;

Yes, I meant this part.


> one can change it before choosing the file to debug.   You seem to
> suggest that -nx was "good enough" before.  If that was good enough
> before (and that's a big "if"), why is changing the search path first
> not also "good enough".

Now instead of just -nx one has to use also "set auto-load-scripts off",
use -ex "file X" and -ex "core-file Y" instead of just X and Y to get that
"set auto-load-scripts off" executed first,
use beforehand -ex "set libthread-db-search-path /foo", OK, that may be enough
if I did not miss anything else.

I admit I did not know about "set auto-load-scripts off" myself until
recently.


> As for Python auto-loading, if -nx was good enough before (and if one
> *really* wanted to run gdb in a security hardened environment one
> would use a secured VM or some such anyway ...), then why isn't
> turning off auto-loading of Python scripts ahead of time also good
> enough?

Yes, it is, it is just too complicated, similiar to the extra VM.  I plan to
just merge the paragraph above into some user-accessible command-line option
"-safe".  I am just not sure how to load pretty printers from system libraries
which are safe but which do not get loaded after "set auto-load-scripts off".


Thanks,
Jan


  reply	other threads:[~2012-01-17 17:49 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-17 10:16 Jan Kratochvil
2012-01-17 12:34 ` Eli Zaretskii
2012-01-17 13:42   ` Joel Brobecker
2012-01-17 14:49     ` [patch 7.4] Deprecate local .gdbinit [Re: [patch] New set auto-load-local-gdbinit + disable it by default] Jan Kratochvil
2012-01-17 16:22       ` Doug Evans
2012-01-17 20:22   ` [patch] New set auto-load-local-gdbinit + disable it by default Tom Tromey
2012-01-17 16:15 ` Doug Evans
2012-01-17 16:34   ` Jan Kratochvil
2012-01-17 16:48     ` Doug Evans
2012-01-17 17:27       ` Jan Kratochvil
2012-01-17 17:33         ` Doug Evans
2012-01-17 17:55           ` Jan Kratochvil [this message]
2012-01-17 18:29             ` Eli Zaretskii
2012-01-17 18:35               ` Jan Kratochvil
2012-01-17 19:54                 ` Tom Tromey
2012-01-17 18:31             ` Doug Evans
2012-01-17 18:44               ` Jan Kratochvil
2012-01-17 19:12                 ` Doug Evans
2012-01-17 19:20                   ` Jan Kratochvil
2012-01-17 19:55               ` Tom Tromey
2012-01-17 20:24                 ` Pedro Alves
2012-01-17 20:26                   ` Tom Tromey
2012-01-17 20:35                   ` Jan Kratochvil
2012-01-17 20:56                     ` Pedro Alves
2012-01-17 19:30           ` Matt Rice
2012-01-17 19:37             ` Jan Kratochvil
2012-01-17 20:26             ` Tom Tromey
2012-01-17 18:00     ` Eli Zaretskii
2012-01-17 18:28       ` Jan Kratochvil
2012-01-17 18:43         ` Eli Zaretskii
2012-01-17 19:02           ` Jan Kratochvil
2012-01-17 20:29         ` Tom Tromey
2012-01-17 20:49           ` Jan Kratochvil
2012-01-17 20:54             ` Doug Evans
2012-01-17 21:10             ` Tom Tromey
2012-01-17 21:13           ` Eli Zaretskii
2012-01-17 21:14             ` Tom Tromey
2012-01-18  4:26               ` Joel Brobecker
2012-01-18 19:38                 ` Jan Kratochvil
2012-01-18 20:01                   ` Doug Evans
2012-01-19  6:30                   ` Joel Brobecker
2012-01-19 12:57                     ` [commit] rm gdb/testsuite/.gdbinit [Re: [patch] New set auto-load-local-gdbinit + disable it by default] Jan Kratochvil
2012-01-19 21:07                   ` [patch] New set auto-load-local-gdbinit + disable it by default Tom Tromey
2012-01-19 21:47                     ` Jan Kratochvil
2012-01-19 21:53                       ` Doug Evans
2012-01-20  4:11                         ` Jan Kratochvil
2012-01-19 21:06                 ` Tom Tromey
2012-01-17 22:16             ` Doug Evans
2012-01-18  3:05               ` Tom Tromey
2012-01-17 16:26 ` Matt Rice
2012-01-17 16:57   ` Doug Evans
2012-01-17 20:09 ` Tom Tromey
2012-01-24  0:33 ` Stan Shebs
2012-01-24 15:54   ` Jan Kratochvil

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120117174839.GA8459@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox