public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: hx w <ye_hx_w@yahoo.com.cn>
To: gcc mail-list gcc <gcc@gcc.gnu.org>, ia64 <ia64-list@redhat.com>,
	RHEL3 RHEL3 <Taroon-list@redhat.com>
Subject: Re: large array, ia64, "segmentation fault"
Date: Sat, 27 Nov 2004 08:27:00 -0000	[thread overview]
Message-ID: <20041127032730.68740.qmail@web15307.mail.bjs.yahoo.com> (raw)
In-Reply-To: <20041127021305.CDB229842C@baradas.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312, Size: 1084 bytes --]


Excuse me , In the REHL3 64bit platform ,how many can
i increase the stack size? I mean the maximum size.

Thanks!!


 --- Peter Barada <peter@the-baradas.com> µÄÕýÎÄ£º
> 
> >I compile a source , when N=100, everything is
> good;
> >but 
> >when i modify N=1000, i got the info: segmentation
> >fault. i am using icc 8.1.
> >
> >My sys info:
> >RHEL3-64bit update 2.
> >2.4.21-4.EL kernel
> >4-way Iatnium2 .
> >8G RAM.
> 
> You're trying to allocate a *large* amount of data
> off the stack int
> hte function main, probably enought to blow the
> limit on the stack
> size.  Look up the manual page for 'ulimit' and use
> that command (with
> the appropriate parameters) to increase the stack
> size limit
> 
> Your other choice is to move the definition oft
> A,B,C outside of main
> so they will be declared globally...
> 
> -- 
> Peter Barada
> peter@the-baradas.com
>  

_________________________________________________________
Do You Yahoo!?
×¢²áÊÀ½çÒ»Á÷Æ·ÖʵÄÑÅ»¢Ãâ·ÑµçÓÊ
http://cn.rd.yahoo.com/mail_cn/tag/1g/*http://cn.mail.yahoo.com/

  reply	other threads:[~2004-11-27  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27  2:43 hx w
2004-11-27  2:46 ` Peter Barada
2004-11-27  8:27   ` hx w [this message]
2004-11-27 23:42     ` Mike Stump
2004-11-28  3:50       ` Dave Korn
2004-11-29 19:15     ` David Mosberger
2004-11-29 19:30       ` Joe Buck
2004-11-29  9:12 Luck, Tony

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=20041127032730.68740.qmail@web15307.mail.bjs.yahoo.com \
    --to=ye_hx_w@yahoo.com.cn \
    --cc=Taroon-list@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=ia64-list@redhat.com \
    /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).