Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ping: [patch 4/6] testsuite: Unify to lib/prelink-support.exp
Date: Mon, 05 Jul 2010 17:35:00 -0000	[thread overview]
Message-ID: <20100705173452.GB2595@adacore.com> (raw)
In-Reply-To: <20100704101823.GD6875@host0.dyn.jankratochvil.net>

> gdb/testsuite/
> 2010-07-04  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 	    Joel Brobecker  <brobecker@adacore.com>
> 
> 	* gdb.base/attach-pie-misread.exp: Load prelink-support.exp.  Replace
> 	build_executable by build_executable_own_libs.  Replace "prelink -R"
> 	execution by a call of prelink_yes.  Comment why "prelink -r" needs no
> 	change.
> 	* gdb.base/break-interp.exp: Load prelink-support.exp.  Rename calls of
> 	copy to file_copy.  Move setting opts --dynamic-linker and -rpath,
> 	mkdir $dir and ldd its parsing and copying to lib/prelink-support.exp.
> 	Replace build_executable by build_executable_own_libs's function
> 	build_executable_own_libs.
> 	(prelinkNO): Create new stub to call prelink_no.
> 	(prelinkYES): Create new stub to call prelink_yes.
> 	(test_attach): Rename calls of copy to file_copy.
> 	(section_get, prelinkNO_run, prelinkNO, prelinkYES, symlink_resolve)
> 	(copy): Move to ...
> 	* lib/prelink-support.exp: ... a new file.  Rename prelinkNO to
> 	prelink_no, prelinkYES to prelink_yes, copy to file_copy.
> 	* gdb.base/prelink.exp: Disable testcase also for is_remote and
> 	skip_shlib_tests.  Load prelink-support.exp.  Replace gdb_compile with
> 	special flags by gdb_compile_shlib.  Replace second gdb_compile by
> 	build_executable_own_libs.  Replace "prelink -R" execution by a call of
> 	prelink_yes.  Replace "prelink -u" and second "prelink -R" execution by
> 	a second call of prelink_yes.  Replace restart commands by
> 	clean_restart.
> 	(prelink): Rename to ...
> 	(seen displacement message): ... this test.  Extend its expectation
> 	strictness.

OK to commit.

> +    # For normal prelink (prelink_yes call) we need to supply $prelink_args.
> +    # For the prelink `-r' option below $prelink_args is not required.
> +    # Moreover if it would be used the problem would not longer be reproducible
> +    # as the libraries would also get relocated.

Minor editorial changes (mostly adding comas)...

    # For normal prelink (prelink_yes call), we need to supply $prelink_args.
    # For the prelink `-r' option below, $prelink_args is not required.
    # Moreover, if it was used, the problem would not longer be reproducible
    # as the libraries would also get relocated.

-- 
Joel


  reply	other threads:[~2010-07-05 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 16:18 Jan Kratochvil
2010-06-09 15:09 ` ping: " Jan Kratochvil
2010-06-29 21:56   ` Joel Brobecker
2010-07-04 10:18     ` Jan Kratochvil
2010-07-05 17:35       ` Joel Brobecker [this message]
2010-07-05 18:11         ` 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=20100705173452.GB2595@adacore.com \
    --to=brobecker@adacore.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