I am running gcc version 4.6.3 so it isn't that. I too wasn't having
any problems with my older Sparc systems, Ultra 5 and Blade 100.
Without Xorg running my kernel compiling hasn't been interrupted by
the Bus error. I have also been running into a known bug with the
kernel http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648766 that
I am going to try and set up a kernel debugging environment and
start trying to find the problem. I feel like all these problems I
have are related.|
On 04/02/2012 01:10 PM, Patrick Baggett wrote:
I run Xorg with nouveau on that Ultra10 and I too get
bus errors from nouveau, but I do compiles all the time without
problem. I understand that the problem is intermittent -- perhaps
it is related to an older GCC version? I'm using GCC 4.6.x and I
have no problems what so ever.
On Mon, Apr 2, 2012 at 11:59 AM, Kieron
The problem is that
there is no particular case that it Bus Errors on with
gcc. I am right now trying to see if the random Bus Errors
have anything to do with the nouveau driver giving me
Kernel unaligned access errors. So right now I am having
this system compile the Linux kernel without Xorg running
which when Xorg was running the Bus Error happened with
the unaligned access errors. So it may just be this driver
bug I have been having.
On 04/02/2012 10:57 AM, Patrick Baggett wrote:
I haven't had any bus errors
while compiling, and I do a fairly good bit of it on
a Sun Ultra 10 (UltraSPARC IIi, not IIIi like the
Blade 2500). Do have a *.c/*.cpp test case I can
try to compile that gives you SIGBUS? Also, what
version of GCC are you using?
On Sun, Apr 1, 2012 at
8:09 PM, Kieron Gillespie <firstname.lastname@example.org>
I recently got a Sun Blade 2500, and have been
trying to track down some bugs. But one bug
that I have constantly noticed is that gcc
will randomly get an Internal Compiler error:
Bus error message. Now all I normally have to
do is rerun the compiler and the error doesn't
occur again. Though this is quite troubling
and I was wondering if anyone has any idea
what could be causing it?
To UNSUBSCRIBE, email to debian-sparc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble?
Archive: [🔎] 4F78FC35.email@example.com"