Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Sanity check PIE displacement (like the PIC one)
Date: Thu, 11 Feb 2010 19:43:00 -0000	[thread overview]
Message-ID: <m31vgrsgmz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100201012004.GA6015@host0.dyn.jankratochvil.net> (Jan 	Kratochvil's message of "Mon, 1 Feb 2010 02:20:04 +0100")

>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:

Thanks for pinging this patch.

Jan> The current PIC message being printed "all the time" is:
Jan> warning: .dynamic section for "/lib64/librt-2.11.1.so" is not at the expected address
Jan> warning: difference appears to be caused by prelink, adjusting expectations
[...]
Jan> I do not find the current PIC message too useful (moreover without
Jan> any offset printed).  Therefore I am open to removing both the PIC
Jan> (and new PIE) messages when the offset is successfuly considered as
Jan> valid.

I don't find that PIC message particularly useful, either.
Is there some situation where that information is helpful?
If not, then IMO we should remove it.

Jan> 2010-02-01  Jan Kratochvil  <jan.kratochvil@redhat.com>
Jan> 	* solib-svr4.c (LM_ADDR_CHECK): Move variable align to a more inner
Jan> 	block.  New variable minpagesize, set it for ELF ABFDs.  New comment on
Jan> 	PPC-aware condition.  Extend the condition using MINPAGESIZE.
Jan> 	(svr4_exec_displacement): New variable retval.  Sanity check it.

Most of it seems reasonable to me.

Jan> +      warning (_("Using PIE (Position Independent Executable) displacement %s "
Jan> +		 "for \"%s\""),
Jan> +	       paddress (target_gdbarch, retval), bfd_get_filename (exec_bfd));

This is printed unconditionally.  But again, when would it matter to the
user?

If it isn't directly informative, I think we should prefer to be silent.
If it is needed in some obscure situation, maybe we can add an equally
obscure command to print it.

What do you think?

Tom


  parent reply	other threads:[~2010-02-11 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-01  1:20 Jan Kratochvil
2010-02-11 16:37 ` [ping] " Jan Kratochvil
2010-02-11 19:43 ` Tom Tromey [this message]
2010-02-11 20:05   ` Daniel Jacobowitz
2010-02-11 21:47     ` Tom Tromey
2010-02-11 22:21     ` Jan Kratochvil
2010-02-11 22:26       ` Daniel Jacobowitz
2010-02-11 23:16         ` Jan Kratochvil
2010-02-13 12:05         ` Jan Kratochvil
2010-02-13 20:14 ` [cancelled] " 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=m31vgrsgmz.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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