public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/29318] [gdb] FAIL: gdb.base/gcore-relro-pie.exp: x/i $pc
Date: Mon, 04 Jul 2022 19:19:05 +0000	[thread overview]
Message-ID: <bug-29318-4717-aI6TGyLkpC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29318-4717@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> That seems to be caused by this alignment mismatch introduced by strip:
> ...
> $ readelf -l -W  gcore-relro-pie | grep GNU_ST
>   GNU_STACK      0x000000 0x0000000000000000 0x0000000000000000 0x000000
> 0x000000 RW  0x10
> $ readelf -l -W  gcore-relro-pie.stripped | grep GNU_ST
>   GNU_STACK      0x000000 0x0000000000000000 0x0000000000000000 0x000000
> 0x000000 RW  0x8
> ...
> 
> I have not been able to reproduce this outside the specific setup, so the
> strip problem may be specific to the package.
> 

I was able to reproduce this with binutils trunk from today, using
--disable-separate-code, which has an effect here in bfd/elf64-x86-64.c:
...
#if DEFAULT_LD_Z_SEPARATE_CODE
# define ELF_MAXPAGESIZE                    0x1000
#else
# define ELF_MAXPAGESIZE                    0x200000
#endif
...
which causes elf_is_p_align_valid to behave differently, which is called from
copy_elf_program_header.

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

  reply	other threads:[~2022-07-04 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 19:08 [Bug symtab/29318] New: " vries at gcc dot gnu.org
2022-07-04 19:19 ` vries at gcc dot gnu.org [this message]
2022-07-05  7:37 ` [Bug symtab/29318] " vries at gcc dot gnu.org

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-29318-4717-aI6TGyLkpC@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).