From: Arjan van de Ven <arjanv@redhat.com>
To: "Andrei A. Voropaev" <av@simcon-mt.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: large auto variables cause segfault under 2.6
Date: Tue, 05 Oct 2004 15:40:52 +0200 [thread overview]
Message-ID: <1096983652.9975.5.camel@laptop.fenrus.com> (raw)
In-Reply-To: <20041005132741.GD28160@avorop.local>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On Tue, 2004-10-05 at 15:27, Andrei A. Voropaev wrote:
> Declaring very large auto variables cause segfaults in the program under
> 2.6 kernel.
>
> Take a look at this program.
>
> int main( int argc, char **argv )
> {
> unsigned char bRet = 0;
>
> char tst[67123456];
>
you have a stack variable that is several orders of magnitude bigger
than the rlimit you have set for the stack I suspect. Try increasing the
stack rlimit...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-05 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 13:27 PROBLEM: large auto variables cause segfault under 2.6 Andrei A. Voropaev
2004-10-05 13:40 ` Arjan van de Ven [this message]
2004-10-05 13:47 ` Andrei A. Voropaev
2004-10-07 15:05 ` Tonnerre
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=1096983652.9975.5.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=av@simcon-mt.com \
--cc=linux-kernel@vger.kernel.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.