 |
 |
bus error
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Aug 2001
Status:
Offline
|
|
... long and rocky road with sourceforge...
Ok, so i finally got this proggie (libmpeg2 and mpeg2dec) to compile with the altivec code... but when I run it with AltiVec, it gives me an error that says "bus error" and then terminates. When AltiVec is flagged to be turned off on the command line, the proggie works.
Is the problem in sourceforges AltiVec code, or have I not passed the right arguments into CC... I'm using -faltivec...
TIA,
David
|
|
|
| |
|
|
|
|
|
|
|
Fresh-Faced Recruit
Join Date: Nov 2001
Location: Melboune, Australia
Status:
Offline
|
|
Originally posted by LordRPI:
<STRONG>... long and rocky road with sourceforge...
Ok, so i finally got this proggie (libmpeg2 and mpeg2dec) to compile with the altivec code... but when I run it with AltiVec, it gives me an error that says "bus error" and then terminates. When AltiVec is flagged to be turned off on the command line, the proggie works.
Is the problem in sourceforges AltiVec code, or have I not passed the right arguments into CC... I'm using -faltivec...
TIA,
David</STRONG>
I thought a bus error was a fancy name for a segmentation fault, but don't hold me to that definition.
|
|
|
| |
|
|
|
|
|
|
|
Admin Emeritus  Join Date: Oct 2000
Location: Boston, MA
Status:
Offline
|
|
Looks like there's a slight difference between the segfault and bus errors. I just tested, and when I tried to write to (int *)0, it gave a bus error, and when I incremented a pointer beyond its bounds it gave a segfault.
It may have something to do with kernel vs. hardware detection, but that's just a total guess.
|
|
"Against stupidity, the gods themselves contend in vain" (Schiller)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
Top