From: Niklaus <niklaus@gmail.com>
To: "Puetz, Oliver P11M22" <Puetz.Oliver@siemens.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: g++ 3.01 on HP-UX 11.0, stack size too large?
Date: Wed, 05 Apr 2006 09:31:00 -0000 [thread overview]
Message-ID: <85e0e3140604050231jaafc69cy3c472d0fda772bca@mail.gmail.com> (raw)
In-Reply-To: <7FC214BA59B6144A9ABDE5C39E8E0098801487@DBGR1EMA.ww007.siemens.net>
On 4/5/06, Puetz, Oliver P11M22 <Puetz.Oliver@siemens.com> wrote:
> Hi,
>
> I've written a program, which allocates locally (within a subroutine)
> approx. a little bit lesser than 8k of memory (I guess, as there are
> also objects). Mainly float vars. If I increase the number of the float
> vars, the program aborts with a Memory fault (core dump).
>
> Is it possible that the program aborts, if the local var size on the
> stack exceeds 8k? Or can I specify a compiler flag to increase the stack
> size for local variables?
>
Try doing a ulimit -a to see the system set size. You can change it
using ulimit or the function setrlimit.
> Kind regards
>
> Oliver Puetz
>
>
>
prev parent reply other threads:[~2006-04-05 9:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 7:07 WG: " Puetz, Oliver P11M22
2006-04-05 9:31 ` Niklaus [this message]
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=85e0e3140604050231jaafc69cy3c472d0fda772bca@mail.gmail.com \
--to=niklaus@gmail.com \
--cc=Puetz.Oliver@siemens.com \
--cc=gcc-help@gcc.gnu.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).