Mail Archives: djgpp/2004/07/23/06:30:47
>_PLEASE_ always try to do whatever it takes to find out what is the
>source line where it crashes. In your case, since bfdsymify doesn't
>help, run the program under a debugger and disassemble when it
>crashes, then post the results.
>
>People here don't have infinite time to dig into programs written by
>others, so please help them to help you.
sorry, I saw no point in running it through the debugger
since the error occurred at the end of the program
after millions of steps.
Now I see, that it would have crashed with smaller n the same way,
although the first solution occurs at n=16.
So,right, I could have done the gdb-debugging.
Still easier would have been to examine the code again !
I was just deranged by the strange -g , -O2 behaviour
and that it runs correctly with small dummy changes.
Posting the program was not meant that others try to examine it,
but rather maybe compile it on their machine and so see
whether the error is OS- or hardware- or GCC-version related.
Sorry for the trouble and the long thread,
Guenter.
- Raw text -