From: Felipe Contreras <al593181@mail.mty.itesm.mx>
To: linux-kernel@vger.kernel.org
Cc: Teodor Iacob <Teodor.Iacob@astral.kappa.ro>
Subject: Re: Weird make bug in 2.5.22
Date: Wed, 19 Jun 2002 02:01:35 -0500 [thread overview]
Message-ID: <20020619070135.GA124@zion.mty.itesm.mx> (raw)
In-Reply-To: <20020618064526.GA27319@linux.kappa.ro>
On Tue, Jun 18, 2002 at 09:45:26AM +0300, Teodor Iacob wrote:
> 139 return code means that the process that make was running
> crashed with signal 11 ( 128 + 11 ) Segmentation Fault so
> perhaps you have some other kind of problems? like a faulty machine?
If you consider a "faulty machine" a development one, then yes, I have one. I
have glibc-2.2.5 gcc-3.1 linux-2.5.23, but that shouldn't matter I want to know
what's causing this and I'll like to fix it.
I'm pretty sure this started with linux-2.5.19, might be it has something to do
with forking, might be it's a make bug, but I think something is wrong here.
--
Felipe Contreras
prev parent reply other threads:[~2002-06-19 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 6:40 Felipe Contreras
2002-06-18 6:45 ` Teodor Iacob
2002-06-19 7:01 ` Felipe Contreras [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=20020619070135.GA124@zion.mty.itesm.mx \
--to=al593181@mail.mty.itesm.mx \
--cc=Teodor.Iacob@astral.kappa.ro \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®