[haiku-development] Re: GCC4 stability issues
- From: Maurice Kalinowski <haiku@xxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sun, 03 Feb 2008 11:16:18 +0100
Hi all,
Has anyone tried running a gcc4 build on real hardware recently? It
seems incredibly unstable compared to the gcc2 equivalent
I can second that.
Additionally I had the problem, that no syslog is written to the bfs
partition. In case you are trying to copy a file , it seems to work
(probably because it's cached and not flushed to disc yet). But as soon
as you try to call sync afterwards, it KDL's too.
I guess that the flush simply does not work on the gcc4 build and your
described crash happens, when the registrar is trying to write things
out to disk (it's supposed to do some work after idleing, if I remember
correctly).
In case you need assistance (by providing 'screenshots' or else how),
feel free to ask.
Regards,
Maurice
- Follow-Ups:
- [haiku-development] Re: GCC4 stability issues
- From: Fredrik Holmqvist
- References:
- [haiku-development] GCC4 stability issues
- From: Rene Gollent
Other related posts:
- » [haiku-development] GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
- » [haiku-development] Re: GCC4 stability issues
Has anyone tried running a gcc4 build on real hardware recently? It seems incredibly unstable compared to the gcc2 equivalent
- [haiku-development] Re: GCC4 stability issues
- From: Fredrik Holmqvist
- [haiku-development] GCC4 stability issues
- From: Rene Gollent