public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29899] Fix for bz#20305 broke glibc on alpha-linux-gnu
Date: Tue, 13 Dec 2022 20:38:00 +0000	[thread overview]
Message-ID: <bug-29899-131-JtpjDUMcBc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29899-131@http.sourceware.org/bugzilla/>

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

--- Comment #2 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to H.J. Lu from comment #1)
> What are values of SIGSTKSZ and MINSIGSTKSZ before and after the commit?

I'm not sure how to read out those values as I tried it with small test program
which crashes after the commit.

Without commit, I get:

(sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$ /bz20305 
The value of SIGSTKSZ is 16384.
The value of MINSIGSTKSZ is 4096.
(sid-alpha-sbuild)glaubitz@z6:~/glibc-git/build$

I used the following test program:

#include <stdio.h>
#include <signal.h>

int main() {

        printf("The value of SIGSTKSZ is %d.\n", SIGSTKSZ);
        printf("The value of MINSIGSTKSZ is %d.\n", MINSIGSTKSZ);

        return 0;
}

Do you have any other suggestion for dumping the values?

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

  parent reply	other threads:[~2022-12-13 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 17:43 [Bug libc/29899] New: " glaubitz at physik dot fu-berlin.de
2022-12-13 17:43 ` [Bug libc/29899] " glaubitz at physik dot fu-berlin.de
2022-12-13 17:43 ` glaubitz at physik dot fu-berlin.de
2022-12-13 19:52 ` hjl.tools at gmail dot com
2022-12-13 20:38 ` glaubitz at physik dot fu-berlin.de [this message]
2022-12-13 21:12 ` hjl.tools at gmail dot com
2022-12-13 21:22 ` glaubitz at physik dot fu-berlin.de
2022-12-14  7:45 ` sam at gentoo dot org
2022-12-14  7:53 ` glaubitz at physik dot fu-berlin.de
2022-12-14 16:00 ` hjl.tools at gmail dot com
2022-12-21 10:25 ` glaubitz at physik dot fu-berlin.de
2022-12-30 14:35 ` glaubitz at physik dot fu-berlin.de

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-29899-131-JtpjDUMcBc@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).