public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11786] PIE support may not work for some PIEs
Date: Fri, 08 Nov 2013 00:45:00 -0000	[thread overview]
Message-ID: <bug-11786-4717-L1mj92b48d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11786-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=11786

--- Comment #12 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
       via  204b53315d81361b008036d93c355ab1f2a44997 (commit)
      from  459d52c84aa5eee986006b793794e382861c073d (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=204b53315d81361b008036d93c355ab1f2a44997

commit 204b53315d81361b008036d93c355ab1f2a44997
Author: Doug Evans <dje@google.com>
Date:   Thu Nov 7 16:43:39 2013 -0800

    PR 11786
    *  solib-svr4.c (svr4_exec_displacement): Ignore filesz, memsz, flags
    and align fields for PT_GNU_RELRO segments.

    testsuite/
    * gdb.base/gcore-relro-pie.c: New file.
    * gdb.base/gcore-relro-pie.exp: New file.

-----------------------------------------------------------------------

Summary of changes:
 gdb/ChangeLog                              |    6 ++
 gdb/solib-svr4.c                           |   44 ++++++++++++++++
 gdb/testsuite/ChangeLog                    |    6 ++
 gdb/testsuite/gdb.base/gcore-relro-pie.c   |   41 +++++++++++++++
 gdb/testsuite/gdb.base/gcore-relro-pie.exp |   75 ++++++++++++++++++++++++++++
 5 files changed, 172 insertions(+), 0 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/gcore-relro-pie.c
 create mode 100644 gdb/testsuite/gdb.base/gcore-relro-pie.exp

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-11-08  0:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11786-4717@http.sourceware.org/bugzilla/>
2013-09-05 20:41 ` dje at google dot com
2013-09-05 20:59 ` jan.kratochvil at redhat dot com
2013-09-05 21:37 ` dje at google dot com
2013-09-05 21:45 ` dje at google dot com
2013-09-06  7:10 ` jan.kratochvil at redhat dot com
2013-09-06  7:13 ` jan.kratochvil at redhat dot com
2013-09-06 16:03 ` ppluzhnikov at google dot com
2013-09-06 16:42 ` dje at google dot com
2013-09-06 17:04 ` jan.kratochvil at redhat dot com
2013-10-25 18:56 ` dje at google dot com
2013-11-04 22:15 ` dje at google dot com
2013-11-08  0:45 ` cvs-commit at gcc dot gnu.org [this message]
2013-12-13 16:52 ` cvs-commit at gcc dot gnu.org
2014-05-12 15:36 ` derek.cole at gmail dot com
2014-05-12 16:13 ` jan.kratochvil at redhat dot com
2015-09-07  4:05 ` xdje42 at gmail dot com
2024-01-14 14:36 ` ssbssa at sourceware dot org
2010-07-02 17:14 [Bug gdb/11786] New: " jan dot kratochvil at redhat dot com
2010-08-12  8:28 ` [Bug gdb/11786] " devurandom at gmx dot net

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=bug-11786-4717-L1mj92b48d@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).