- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Im running a quite complicated code, and after thousands of iterations I get this:
forrtl: severe (180): SIGBUS, bus error occurred
Image PC Routine Line Source
a.out 000770F7 Unknown Unknown Unknown
a.out 00076593 Unknown Unknown Unknown
a.out 00040DB6 Unknown Unknown Unknown
a.out 0001C78E Unknown Unknown Unknown
a.out 0002311C Unknown Unknown Unknown
libSystem.B.dylib 9586597B Unknown Unknown Unknown
Unknown FFFFFFFF Unknown Unknown Unknown
a.out 0000ED3E Unknown Unknown Unknown
a.out 0000EFED Unknown Unknown Unknown
a.out 00001DD2 Unknown Unknown Unknown
a.out 00001D8C Unknown Unknown Unknown
a.out 00001CB9 Unknown Unknown Unknown
Unknown 00000001 Unknown Unknown Unknown
Anyone have a clue to what this means?
Thanks,
Sebastian
forrtl: severe (180): SIGBUS, bus error occurred
Image PC Routine Line Source
a.out 000770F7 Unknown Unknown Unknown
a.out 00076593 Unknown Unknown Unknown
a.out 00040DB6 Unknown Unknown Unknown
a.out 0001C78E Unknown Unknown Unknown
a.out 0002311C Unknown Unknown Unknown
libSystem.B.dylib 9586597B Unknown Unknown Unknown
Unknown FFFFFFFF Unknown Unknown Unknown
a.out 0000ED3E Unknown Unknown Unknown
a.out 0000EFED Unknown Unknown Unknown
a.out 00001DD2 Unknown Unknown Unknown
a.out 00001D8C Unknown Unknown Unknown
a.out 00001CB9 Unknown Unknown Unknown
Unknown 00000001 Unknown Unknown Unknown
Anyone have a clue to what this means?
Thanks,
Sebastian
コピーされたリンク
6 返答(返信)
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
This is the Mac OS equivalent of what Linux calls SIGSEGV. Could be anything.
compile and link with -g -traceback. Yes, you can use those with optimized code.
This will hopefully give you a better stack traceback so you can find where you code is getting the seg violation.
You can also try the -check options, -check all for example, -fp-stack-check is another good one to use.
what stacksize do you have for your shell environment? Check that also.
ron
compile and link with -g -traceback. Yes, you can use those with optimized code.
This will hopefully give you a better stack traceback so you can find where you code is getting the seg violation.
You can also try the -check options, -check all for example, -fp-stack-check is another good one to use.
what stacksize do you have for your shell environment? Check that also.
ron
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I compiled with -g -checkbounds -traceback and I get this message:
forrtl: severe (408): fort: (3): Subscript #2 of the array IHEAD has value 0 which is less than the lower bound of 1
and yes IHEAD is an array in my code, I just don't understand why its getting messed up. It seems like that error is the results of something else.
The stacksize was 8192 - I have maxed it out to 65532; I'll see what that does.
Thanks,
Sebastian
forrtl: severe (408): fort: (3): Subscript #2 of the array IHEAD has value 0 which is less than the lower bound of 1
and yes IHEAD is an array in my code, I just don't understand why its getting messed up. It seems like that error is the results of something else.
The stacksize was 8192 - I have maxed it out to 65532; I'll see what that does.
Thanks,
Sebastian
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
I doubt it will do much. You have a coding error in the program that is accessing IHEAD with a zero index. The traceback should tell you exactly where in the code this is.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hmm I compiled with traceback but all that was shown was:
forrtl: severe (408): fort: (3): Subscript #2 of the array IHEAD has value 0 which is less than the lower bound of 1
Image PC Routine Line Source
a.out 00088EB7 Unknown Unknown Unknown
a.out 00088353 Unknown Unknown Unknown
a.out 00052B7A Unknown Unknown Unknown
a.out 0002E552 Unknown Unknown Unknown
a.out 0002DAF9 Unknown Unknown Unknown
a.out 0000CC75 Unknown Unknown Unknown
a.out 00020B02 Unknown Unknown Unknown
a.out 00020DB1 Unknown Unknown Unknown
a.out 000018C2 Unknown Unknown Unknown
a.out 0000187C Unknown Unknown Unknown
a.out 000017A9 Unknown Unknown Unknown
Unknown 00000001 Unknown Unknown Unknown
forrtl: severe (408): fort: (3): Subscript #2 of the array IHEAD has value 0 which is less than the lower bound of 1
Image PC Routine Line Source
a.out 00088EB7 Unknown Unknown Unknown
a.out 00088353 Unknown Unknown Unknown
a.out 00052B7A Unknown Unknown Unknown
a.out 0002E552 Unknown Unknown Unknown
a.out 0002DAF9 Unknown Unknown Unknown
a.out 0000CC75 Unknown Unknown Unknown
a.out 00020B02 Unknown Unknown Unknown
a.out 00020DB1 Unknown Unknown Unknown
a.out 000018C2 Unknown Unknown Unknown
a.out 0000187C Unknown Unknown Unknown
a.out 000017A9 Unknown Unknown Unknown
Unknown 00000001 Unknown Unknown Unknown
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hmm. I suppose you could add print statements in various places in your program to try to identify the particular use of array IHEAD.
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
IHEAD is used to identify a spacial sector that a particle is in. As I suspected, it was being accessed incorrectly because a particle(s) had moved out of bounds. I fixed it by making the boundaries larger - the problem I'm trying to figure out is why are the particles doing this (they shouldn't). Anywho, its my problem. Thank you very much for helping me ID those run-time error messages.
Regards,
Sebastian
Regards,
Sebastian
