Re: backtrace a segfault

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 04/09/2015 09:06 AM, Patrick Begou wrote:
Hi,

I'm working on a large parallel fortran application which give (sometime) a segfault. When this error occurs I would like to backtrace the call stack to know where it takes place but I'm unable to get this information, no more than a list of memory addresses. I've build a small test-case (with an error in array dimension creating a segmentation fault in a subroutine ) to investigate gfortran/gcc options.

Sometimes I'm debugging MPICH/C++ programs old style.
In C++ you can attach output files e.g. to stdout, with std::cout.rdbuf(...).
So each MPI Process gets a separate file.
vimdiff can open multiple files and compare them side by side.
Another useful tool from MPICH is jumpshot for visualizing the MPI calls.

-A.




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux