Hi all,
I can tell now for sure, that all SIG11 and SIG4 problems are
gone with make buildworld, if I compile here
make(8)
rm(8)
mkdir(8)
with -g -ggdb
If I don't do that, make world stops after 4 - 30 seconds. So it
could be definitly some optimizing bug in our gcc. And this bug
seems to be
Martin Blapp wrote:
> Now rm(1) and make(1) coredump with sig 10. So I thought it
> would be a good idea to recompile them with -g -ggdb and
> retry.
>
> Now the strange part. The coredumps are gone. Ok, I did not
> use -pipe then. I'll will now try to use -pipe and -g and -ggdb
> all together.
>
Hi,
I see here now very strange effects. I've upgraded to the
newest CURRENT yesterday, installed on the PIV machine
over NFS.
Now rm(1) and make(1) coredump with sig 10. So I thought it
would be a good idea to recompile them with -g -ggdb and
retry.
Now the strange part. The coredumps are gon
> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > Try disabling -pipe when building the compiler. This seems to make
> > things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> > building the kernel with -pipe sometimes produces a kernel that
> > subsequently murders
Hi,
I have to take back that a kernel from april 3. runs fine.
It happens there too, but few times than on recent current.
The build lives for 5 minutes, instead of 30 seconds. Then
I get a SIG4 as usual and cc crashes.
Anybody has a idea to which date I can switch back to
have my problem solv
Hi all,
The problem must have been introduced after April, 3.
I've a kernel.old from this date which runs perfectly.
Maybe this can help to track the bug down.
Martin
Martin Blapp, <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
--
ImproW
On Sat, May 04, 2002 at 21:54:08 +0200, Martin Blapp wrote:
> Hi all,
>
> I experiment very strange problems here at the moment with
> a new server.
>
> Buildworld survives about 30 secondy, the errors are SIG4 (90%)
> and SIG11 (10%). And I cannot compile any important programs :-/
>
> I've ex
On Sun, 5 May 2002, Bruce Evans wrote:
> On Sat, 4 May 2002, Jake Burkholder wrote:
>
> > Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
> > Bruce Evans said words to the effect of;
> > >
> > > I have seen signs of a generic pipe bug in vi: vi's i/o buffer for
> > > pipes is sometimes
On Sat, 4 May 2002, Jake Burkholder wrote:
> Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
> Bruce Evans said words to the effect of;
> >
> > I have seen signs of a generic pipe bug in vi: vi's i/o buffer for
> > pipes is sometimes invalid (kern/sys_pipe.c:pipe_build_write_buffer()
Apparently, On Sun, May 05, 2002 at 10:44:44AM +1000,
Bruce Evans said words to the effect of;
> On Sat, 4 May 2002, David O'Brien wrote:
>
> > On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > > Try disabling -pipe when building the compiler. This seems to make
> > > th
On Sat, 4 May 2002, David O'Brien wrote:
> On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> > Try disabling -pipe when building the compiler. This seems to make
> > things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> > building the kernel with -pipe sometimes produces
On Sat, May 04, 2002 at 09:26:33PM +0100, Brian Somers wrote:
> Try disabling -pipe when building the compiler. This seems to make
> things more stable here (CFLAGS=-O in /etc/make.conf) - as if
> building the kernel with -pipe sometimes produces a kernel that
> subsequently murders the compil
On Sat, 2002-05-04 at 13:54, Martin Blapp wrote:
>
> Hi all,
>
> I experiment very strange problems here at the moment with
> a new server.
>
> Buildworld survives about 30 secondy, the errors are SIG4 (90%)
> and SIG11 (10%). And I cannot compile any important programs :-/
>
> I've exchanged
Hi,
Try disabling -pipe when building the compiler. This seems to make
things more stable here (CFLAGS=-O in /etc/make.conf) - as if
building the kernel with -pipe sometimes produces a kernel that
subsequently murders the compiler with sig11/sig4 all the time.
This is just marginally more th
I can tell now for sure that it happens on CURRENT only.
I replaced the disk with a STABLE one, same model, and have
completed a make buildworld -j 20 sucessfully.
The CURRENT disk (in this case SCSI, but it happens also on ATA
dumps core a buildworld after 10 - 30 seconds.
Martin
Martin Blap
15 matches
Mail list logo