public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/11786] PIE support may not work for some PIEs
Date: Sun, 14 Jan 2024 14:36:57 +0000	[thread overview]
Message-ID: <bug-11786-4717-O3SsBijGUr@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-11786-4717@http.sourceware.org/bugzilla/>

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

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ssbssa at sourceware dot org

--- Comment #16 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Sourceware Commits from comment #15)
> The master branch has been updated by Simon Marchi <simark@sourceware.org>:
> 
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=be2d111a878e1422c921226bc7714131a5c470fa
> 
> commit be2d111a878e1422c921226bc7714131a5c470fa
> Author: Michael Spang <spang@google.com>
> Date:   Sun Aug 19 10:55:58 2018 -0400
> 
>     Fix debugging of stripped PIE executables with padded PT_TLS
>     
>     Certain PIE executables produced by gold cannot be debugged by gdb after
>     being stripped. GDB requires program headers of PIE executables to match,
>     and those checks may fail due to adjustments made during stripping.
>     
>     One case of this occurs because strip recomputes the memsz of PT_TLS and
>     does not add alignment, while gold does. This is another variant of PR
>     11786, so apply the same fix of relaxing the program header matching.
>     
>     gdb/ChangeLog:
>     
>     	PR gdb/11786
>     	* solib-svr4.c (svr4_exec_displacement): Ignore memsz fields
>     	for PT_TLS segments.
>     
>     gdb/testsuite/ChangeLog:
>     
>     	PR gdb/11786
>     	* gdb.base/gcore-tls-pie.c: New file.
>     	* gdb.base/gcore-tls-pie.exp: New file.

Can this be closed?

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

  parent reply	other threads:[~2024-01-14 14:36 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
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 [this message]
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-O3SsBijGUr@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).