Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch#2 2/6] set auto-load * main part
Date: Thu, 05 Apr 2012 18:25:00 -0000	[thread overview]
Message-ID: <20120405182504.GA13165@host2.jankratochvil.net> (raw)
In-Reply-To: <83vcleb1lb.fsf@gnu.org>

On Thu, 05 Apr 2012 18:11:28 +0200, Eli Zaretskii wrote:
> > 	@cindex Python auto-loading, Python
> 
> Do we really need "Python" twice?

Therefore used:
	@node Python Auto-loading
	@subsection Python Auto-loading
	@cindex Python auto-loading


> > # Be aware that system init file (@pxref{System-wide configuration})
> > # and init files from your home directory (@pxref{Home Directory Init File})
> > # still get read still get read (as they come from generally trusted
> > # directories).  You could use also the @ref{-nx} option to prevent @value{GDBN}
> > # from reading any auto-loaded files instead.
> > 
> > IMO says that -nx will disable even objfile-gdb.py, libthread_db.so.1 etc.
> > auto-loading.  Or at least it is ambiguous in such way.
> 
> Point taken, but then what _did_ you mean by "very every"?

I wanted to say that if you want to prevent loading any kind of file then you
have to use both -nx and "set auto-load no".

IMHO the current paragraph says that if I use -nx then no kind of file gets
loaded.  That is not true.


Thanks,
Jan


  reply	other threads:[~2012-04-05 18:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29  9:12 Jan Kratochvil
2012-03-30  7:20 ` Eli Zaretskii
2012-04-03 18:33   ` Jan Kratochvil
2012-04-05 16:11     ` Eli Zaretskii
2012-04-05 18:25       ` Jan Kratochvil [this message]
2012-04-05 21:20         ` Eli Zaretskii
2012-04-05 21:28           ` Eli Zaretskii
2012-04-05 21:33             ` 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=20120405182504.GA13165@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=eliz@gnu.org \
    --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