From: Matthew Wilcox <willy@debian.org>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: rhirst@linuxcare.com, grundler@dsl2.external.hp.com,
varenet@esiee.fr, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] SMP (in)stability
Date: Mon, 15 Jul 2002 15:05:43 +0100 [thread overview]
Message-ID: <20020715150543.M27706@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200207101744.g6AHiKW0011045@hiauly1.hia.nrc.ca>; from dave@hiauly1.hia.nrc.ca on Wed, Jul 10, 2002 at 01:44:19PM -0400
On Wed, Jul 10, 2002 at 01:44:19PM -0400, John David Anglin wrote:
> Moving the code to hpux11, this is the error that causes the crash:
>
> stage1/xgcc -Bstage1/ -B/opt/gnu/hppa2.0w-hp-hpux11.11/bin/ -c -DIN_GCC -g -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -I. -I. -I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/config -I../../gcc/gcc/../include ../../gcc/gcc/cfgbuil
> d.c -o cfgbuild.o
> Pi 16528 received a SIGSEGV for stck growth ailure.
> Possible caues: insufficient memory or swap space,
> or stack size exceeded maxssiz.
> xgcc: Internal error: Segmentation fault (program cc1)
hrm. i wonder what happens when we run off the top of the stack ...
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-07-15 15:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 2:40 [parisc-linux] SMP (in)stability Jeremy Drake
2002-07-10 5:36 ` Grant Grundler
2002-07-10 7:55 ` Jeremy Drake
2002-07-10 8:51 ` Thibaut VARENE
2002-07-10 9:24 ` Thomas Bogendoerfer
2002-07-10 11:02 ` Thibaut VARENE
2002-07-10 11:35 ` Thibaut VARENE
2002-07-10 14:50 ` Grant Grundler
2002-07-10 14:23 ` Richard Hirst
2002-07-10 17:07 ` John David Anglin
2002-07-10 17:44 ` John David Anglin
2002-07-15 14:05 ` Matthew Wilcox [this message]
2002-07-15 16:15 ` Randolph Chung
2002-07-10 20:34 ` Jeremy Drake
2002-07-14 6:26 ` Jeremy Drake
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=20020715150543.M27706@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=grundler@dsl2.external.hp.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rhirst@linuxcare.com \
--cc=varenet@esiee.fr \
/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.