Hi Halim, you are right, thank you very much. --Ice At 2016-05-09 22:48:39, "Halim Amer" <[email protected]> wrote:
I don't see why you couldn't step into MPI_Get_processor_name, other than you are linking to the wrong MPI implementation that doesn't have debug symbols.
I tested your example with --enable-g=all when building MPICH and it was sufficient to step into MPI_Get_processor_name.
--Halim
On 5/8/16 6:56 AM, 冰 wrote:
Hi, I want to use |gdb| to step into the code to see what's going on inside the code, for example my code as below, I set a break at the line MPI_Get_processor_name (processor_name, &namelen), I want to step into MPI_Get_processor_name, I configure with |--enable-g=all and |--enable-fast=O0, but gdb cann't step into MPI_Get_processor_name, it steps into fprintf, what should I do?
#include "mpi.h" #include <stdio.h> int main (int argc, char **argv) { int myid, numprocs; int namelen; char processor_name[MPI_MAX_PROCESSOR_NAME];
MPI_Init (&argc, &argv); MPI_Comm_rank (MPI_COMM_WORLD, &myid); MPI_Comm_size (MPI_COMM_WORLD, &numprocs); MPI_Get_processor_name (processor_name, &namelen); fprintf (stderr, "Hello World! Process %d of %d on %s\n", myid, numprocs, processor_name); MPI_Finalize (); return 0; }
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss