All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Grant Grundler <grundler@parisc-linux.org>
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: Sat, 13 Aug 2005 08:40:28 -0500	[thread overview]
Message-ID: <1123940428.5037.2.camel@mulgrave> (raw)
In-Reply-To: <20050813050211.GE32609@colo.lackof.org>

On Fri, 2005-08-12 at 23:02 -0600, Grant Grundler wrote:
> I expect this is the difference...I need to use the same g++ version.
> Does someone want to hack a small test program that consumes
> stack space until it bombs out becuase of the ulimit?

Here's a test program that does this:

#include <stdio.h>

char *stack_base_estimate;

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;

	stack_base_estimate = &b;
	printf("Estimating stack base at 0x%p\n", stack_base_estimate);
	recurse();
	return 0;
}
		
But the results are as expected (on 2.6.13-rc6-pa1):

jejb@raven> ulimit -a
core file size        (blocks, -c) 0
data seg size         (kbytes, -d) unlimited
file size             (blocks, -f) unlimited
max locked memory     (kbytes, -l) unlimited
max memory size       (kbytes, -m) unlimited
open files                    (-n) 1024
pipe size          (512 bytes, -p) 8
stack size            (kbytes, -s) 8192
cpu time             (seconds, -t) unlimited
max user processes            (-u) unlimited
virtual memory        (kbytes, -v) unlimited
jejb@raven> a.out
Estimating stack base at 0x0xc0114548
Estimating stack consumed 0x80
[...]
Estimating stack consumed 0x7fefc0
Estimating stack consumed 0x7ff100
Segmentation fault

James


_______________________________________________
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-13 13:40 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 [this message]
2005-08-13 17:46       ` John David Anglin
2005-08-13 19:30         ` John David Anglin
2005-08-16  3:02       ` Randolph Chung
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=1123940428.5037.2.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=grundler@parisc-linux.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.