Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
	PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1
Date: Tue, 16 Aug 2005 11:02:47 +0800	[thread overview]
Message-ID: <43015757.2080207@tausq.org> (raw)
In-Reply-To: <1123940428.5037.2.camel@mulgrave>

Can somebody with a 32-bit machine try this slightly modified test case?
In the presence of a signal handler for SIGSEGV, the program will loop
segfaulting because there's not enough stack space left for the signal
handler. On an a500, this program just loops, but perhaps on a 32-bit
machine it crashes the machine if run long enough. Seems to suggest a
problem in our kernel entry/exit paths?

randolph

================================================================

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

char *stack_base_estimate;

static void sighandler(int sig)
{
        printf("Got signal %d\n", sig);
        exit(0);
}

void
recurse(void)
{
        char a[256];

        memset(a, '\0', sizeof(*a));
        printf("Estimating stack consumed 0x%lx\n",
               (unsigned long)(a - stack_base_estimate));
        recurse();
}

int
main(int argc, char *argv[])
{
        char b;

        signal(SIGSEGV, sighandler);

        stack_base_estimate = &b;
        printf("Estimating stack base at 0x%p\n", stack_base_estimate);
        recurse();
        return 0;
}

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  parent reply	other threads:[~2005-08-16  3:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050812180551.GA32609@colo.lackof.org>
2005-08-13  0:00 ` [parisc-linux] Re: gsyprf11 and 2.6.13-rc3-pa1 John David Anglin
2005-08-13  5:02   ` Grant Grundler
2005-08-13  5:11     ` John David Anglin
2005-08-13  5:14     ` John David Anglin
2005-08-13 13:40     ` James Bottomley
2005-08-13 17:46       ` John David Anglin
2005-08-13 19:30         ` John David Anglin
2005-08-16  3:02       ` Randolph Chung [this message]
2005-08-16  3:18         ` John David Anglin
2005-08-14  1:32 ` John David Anglin
     [not found] <no.id>
2005-08-16  3:32 ` John David Anglin
2005-08-16  9:17 Joel Soete
2005-08-16 10:10 ` Randolph Chung
2005-08-16 13:39   ` John David Anglin
2005-08-16 14:34     ` Randolph Chung
2005-08-16 15:06       ` Michael S. Zick
2005-08-16 23:57     ` Randolph Chung
2005-08-17  0:08       ` John David Anglin
2005-08-17  0:50         ` John David Anglin

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=43015757.2080207@tausq.org \
    --to=randolph@tausq.org \
    --cc=James.Bottomley@SteelEye.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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