public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug build/28555] uclibc compile failure since commit 4655f8509fd44e6efabefa373650d9982ff37fd6
Date: Mon, 08 Nov 2021 18:00:43 +0000	[thread overview]
Message-ID: <bug-28555-4717-KjWkj5l6Sh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28555-4717@http.sourceware.org/bugzilla/>

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

Pedro Alves <pedro at palves dot net> changed:

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

--- Comment #2 from Pedro Alves <pedro at palves dot net> ---
Tromey also ran into something similar on RH ES5:

 https://sourceware.org/pipermail/gdb-patches/2021-May/178801.html

> Or simpler, since this value is not likely to change ever, would be to just do:
> #define GDB_ADDR_NO_RANDOMIZE 0x0040000
> and use that.

That seems fine to me.  This value isn't going to ever change since changing it
would be an ABI break.  The actual trouble would be if different architectures
defined the constant differently, which I don't think is the case.

I have no idea whether uclibc users are able to build unpatched gdb, or if the
uclibc project carries some local patches.  If the latter, maybe we can just
ignore this since it's been fixed for the next release.

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

  parent reply	other threads:[~2021-11-08 18:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-06 12:20 [Bug build/28555] New: " ps.report at gmx dot net
2021-11-08 17:15 ` [Bug build/28555] " simark at simark dot ca
2021-11-08 17:15 ` simark at simark dot ca
2021-11-08 18:00 ` pedro at palves dot net [this message]
2021-11-08 19:16 ` simark at simark dot ca
2021-11-08 19:42 ` tromey at sourceware dot org
2021-11-08 20:42 ` simark at simark dot ca
2021-11-08 21:29 ` tromey at sourceware dot org
2021-11-09 15:29 ` cvs-commit at gcc dot gnu.org
2021-11-09 15:30 ` tromey at sourceware dot org
2021-11-09 18:01 ` ps.report at gmx dot net
2021-11-09 21:26 ` cvs-commit at gcc dot gnu.org
2021-11-09 21:26 ` tromey at sourceware dot 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-28555-4717-KjWkj5l6Sh@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).