From: Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] sim: filter out SIGSTKSZ [PR sim/28302]
Date: Tue, 11 Jan 2022 12:27:59 -0500 [thread overview]
Message-ID: <Yd2+H5NaYwTFCbOt@vapier> (raw)
In-Reply-To: <DM6PR11MB38847B871626E4D473CB890BC4519@DM6PR11MB3884.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
On 11 Jan 2022 15:14, Aktemur, Tankut Baris wrote:
> On Sunday, October 3, 2021 6:09 PM, Mike Frysinger wrote:
> > We map target signals to host signals so we can propagate signals
> > between the host & simulated worlds. That means we need to know
> > the symbolic names & values of all signals that might be sent.
> >
> > The tools that generate that list use signal.h and include all
> > symbols that start with "SIG" so as to automatically include any
> > new symbols that the C library might add. Unfortunately, this
> > also picks up "SIGSTKSZ" which is not actually a signal itself,
> > but a signal related setting -- it's the size of the stack when
> > a signal is handled.
> >
> > By itself this doesn't super matter as we will never see a signal
> > with that same value (since the range of valid signals tend to be
> > way less than 1024, and the size of the default signal stack will
> > never be that small). But with recent glibc changes that make this
> > into a dynamic value instead of a compile-time constant, some users
> > see build failures when building the sim.
> >
> > As suggested by Adam Sampson, update our scripts to ignore this
> > symbol to simplify everything and avoid the build failure.
> >
> > Bug: https://sourceware.org/PR28302
>
> This patch fixes a build problem that may be seen with GDB 11. Should
> it be cherry-picked to gdb-11-branch to be included for the upcoming
> 11.2 release?
i don't normally pay much attention to branches. but i can cherry pick
it back if people want it & branch maintainer approves it.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-01-11 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 16:09 Mike Frysinger via Gdb-patches
2022-01-11 15:14 ` Aktemur, Tankut Baris via Gdb-patches
2022-01-11 17:27 ` Mike Frysinger via Gdb-patches [this message]
2022-01-12 5:05 ` Joel Brobecker via Gdb-patches
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=Yd2+H5NaYwTFCbOt@vapier \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=tankut.baris.aktemur@intel.com \
--cc=vapier@gentoo.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