"Paul" <un******@rmci. net> wrote...
Situation:
Running a MPI program that segfaults.
Cannot open program up in debugger due to nature of MPI system.
Using g++ 3.2.3.
Goal:
Find out which line it segfaults on; ideally which variable name causes
the error. Some kind of error message akin to VC7's "stack corrupted
around varname" message would be very nice.
Less ideally:
I'm told that core dumps aid in finding out what went wrong where.
a)Is a "stack corrupted around" message possible with gcc?
b)How can I force my program to core dump on exceptional exit?
The only relevant term I've found is "variable". MPI, segfault, core
dump, debugger, while are well known, unfortunately mean very little
in a language newsgroup. Unless your problem is proven of a language
kind, you'll be better off in a newsgroup dedicated to your platform
or to your compiler. Since you didn't say what platform it was, I
can't recommend anything in particular, only 'comp.os.<your_ platform>',
but for g++ there is 'gnu.g++.help'.
If you think your problem _is_ of a language kind, please post the code
you think is responsible. Without code there is no real way to help
you.
Victor