Well, the communicator object was getting deleted in the call to MPIR_Comm_release ( invoked by MPID_Request_release()).. The inuse pointer was being returned as 0.As a temporary fix,in MPI_ Init, I have set ref_count paramenter for the comm object as 2. I shall trace through the calls to see if it was getting decremented prior to MPID_Request_release(). Its is working for now and generating the logfile in the ".clog2" format. I executed the clogTOslog2 script and converted the format. <br>
<br>When I try loading the this log file to jumpshot, I get the following text output : <br><span style="color: rgb(0, 0, 153);">GUI_LIBDIR is set. GUI_LIBDIR = /home/kc/mpich-install//lib</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">Java is version 1.4.2.</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Starting the SLOG-2 Display Program .....</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">Jumpshot-4 setup file : /home/kc/.jumpshot4.conf</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Initialize Parameters:</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">Y_AXIS_ROOT_LABEL = SLOG-2</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">INIT_SLOG2_LEVEL_READ = 4</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">AUTO_WINDOWS_LOCATION = true</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">SCREEN_HEIGHT_RATIO = 0.5</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">TIME_SCROLL_UNIT_RATIO = 0.01</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">Y_AXIS_ROOT_VISIBLE = true</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">ACTIVE_REFRESH = false</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">ROW_RESIZE_MODE = Row</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">BACKGROUND_COLOR = black</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">STATE_HEIGHT_FACTOR = 0.9</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">NESTING_HEIGHT_FACTOR = 0.8</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">ARROW_ANTIALIASING = default</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">MIN_WIDTH_TO_DRAG = 4</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">CLICK_RADIUS_TO_LINE = 3</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">LEFTCLICK_INSTANT_ZOOM = true</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">STATE_BORDER = ColorRaised</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">ARROW_HEAD_LENGTH = 10</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">ARROW_HEAD_WIDTH = 6</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">EVENT_BASE_WIDTH = 8</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">PREVIEW_STATE_DISPLAY = CumulativeExclusionRatio</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">PREVIEW_STATE_BORDER = ColorXOR</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">PREVIEW_STATE_BORDER_W = 3</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">PREVIEW_STATE_BORDER_H = 0</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">PREVIEW_STATE_LEGEND_H = 2</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">PREVIEW_ARROW_LOG_BASE = 5</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">SEARCH_ARROW_LENGTH = 20</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">SEARCH_FRAME_THICKNESS = 3</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">SEARCHED_OBJECT_ON_TOP = false</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">HISTOGRAM_ZERO_ORIGIN = true</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">SUMMARY_STATE_BORDER = ColorRaised</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">SUMMARY_ARROW_LOG_BASE = 5</span><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">LEGEND_PREVIEW_ORDER = true</span><br style="color: rgb(0, 0, 153);">
<span style="color: rgb(0, 0, 153);">LEGEND_TOPOLOGY_ORDER = true</span><br style="color: rgb(0, 0, 153);"><br style="color: rgb(0, 0, 153);"><span style="color: rgb(0, 0, 153);">The file block pointer to the Tree Directory is NOT initialized!, can't read it.</span><br style="color: rgb(0, 0, 153);">
<br style="color: rgb(0, 0, 153);"><br> IS there any environment variable that needs to be initialsed? <br><br>Thanks,<br>Krishna Chaitanya K <br><br style="color: rgb(0, 0, 153);"><br style="color: rgb(0, 0, 153);">
<div class="gmail_quote"><span style="color: rgb(0, 0, 153);">O</span>n Thu, Mar 20, 2008 at 4:56 PM, Dave Goodell <<a href="mailto:goodell@mcs.anl.gov">goodell@mcs.anl.gov</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
It's pretty hard to debug this issue via email. However, you could<br>
try running valgrind on your modified MPICH2 to see if any obvious<br>
bugs pop out. When you do, make sure that you configure with "--<br>
enable-g=dbg,meminit" in order to avoid spurious warnings and to be<br>
able to see stack traces.<br>
<font color="#888888"><br>
-Dave<br>
</font><div><div></div><div class="Wj3C7c"><br>
On Mar 19, 2008, at 1:05 PM, Krishna Chaitanya wrote:<br>
<br>
> The problem seems to be with the communicator in MPI_Bcast() (/src/<br>
> mpi/coll/bcast.c).<br>
> The comm_ptr is initialized to NULL and after a call to<br>
> MPID_Comm_get_ptr( comm, comm_ptr ); , the comm_ptr points to the<br>
> communicator object which was created throught MPI_Init().<br>
> However, MPID_Comm_valid_ptr( comm_ptr, mpi_errno ) returns with a<br>
> value other than MPI_SUCCESS.<br>
> During some traces, it used to crash at this point itself. On some<br>
> other traces, it used to go into the progress engine as I described<br>
> in my previous mails.<br>
><br>
> What could be the reason? Hope someone chips in. I havent been able<br>
> to figure this out for sometime now.<br>
><br>
> Krishna Chaitanya K<br>
><br>
> On Wed, Mar 19, 2008 at 8:44 AM, Krishna Chaitanya<br>
> <<a href="mailto:kris.c1986@gmail.com">kris.c1986@gmail.com</a>> wrote:<br>
> This might help :<br>
><br>
> In the MPID_Comm structure, I have included the following line for<br>
> the peruse place-holder :<br>
> struct mpich_peruse_handle_t** c_peruse_handles;<br>
><br>
> And in the function, MPID_Init_thread(), i have the line<br>
> MPIR_Process.comm_world->c_peruse_handles = NULL;<br>
> when the rest of the members of the comm_world structure are being<br>
> populated.<br>
><br>
> Thanks,<br>
> Krishna Chaitanya K<br>
><br>
><br>
><br>
> On Wed, Mar 19, 2008 at 8:19 AM, Krishna Chaitanya<br>
> <<a href="mailto:kris.c1986@gmail.com">kris.c1986@gmail.com</a>> wrote:<br>
> Thanks for the help. I am facing an weird problem right now. To<br>
> incorporate the PERUSE component, I have modified the communicator<br>
> data structure to incude the PERUSE handles. The program executes<br>
> as expected when compiled without the "mpe=mpilog" flag.When I<br>
> compile it with the mpe component, the program gives this output :<br>
><br>
> Fatal error in MPI_Bcast: Invalid communicator, error stack:<br>
> MPI_Bcast(784): MPI_Bcast(buf=0x9260f98, count=1, MPI_INT, root=0,<br>
> MPI_COMM_WORLD) failed<br>
> MPI_Bcast(717): Invalid communicator<br>
><br>
> On tracing further, I understood this :<br>
> MPI_Init () ( log_mpi_core.c )<br>
> -- > PMPI_Init ( the communicator object is created here )<br>
> -- > MPE_Init_log ()<br>
> -- > CLOG_Local_init()<br>
> -- > CLOG_Buffer_init4write ()<br>
> -- > CLOG_Preamble_env_init()<br>
> -- > MPI_Bcast () (bcast.c)<br>
> -- > MPIR_Bcast ()<br>
> -- > MPIC_Recv () /<br>
> MPIC_Send()<br>
> -- > MPIC_Wait()<br>
> < Program crashes ><br>
> The MPIC_Wait function is invoking the progress engine, which<br>
> works properly without the mpe component.<br>
> Even within the progress engine, MPIDU_Sock_wait() and<br>
> MPIDI_CH3I_Progress_handle_sock_event() are executed a couple of<br>
> times before the program crashes in the MPIDU_Socki_handle_read()<br>
> or the MPIDU_Socki_handle_write() functions. ( The read() and the<br>
> write() functions work two times, I think)<br>
> I am finding it very hard to reason why the program crashes<br>
> with mpe. Could you please suggest where I need to look at to sort<br>
> this issue out?<br>
><br>
> Thanks,<br>
> Krishna Chaitanya K<br>
><br>
> On Wed, Mar 19, 2008 at 2:20 AM, Anthony Chan <<a href="mailto:chan@mcs.anl.gov">chan@mcs.anl.gov</a>><br>
> wrote:<br>
><br>
><br>
> On Wed, 19 Mar 2008, Krishna Chaitanya wrote:<br>
><br>
> > Hi,<br>
> > I tried configuring MPICH2 by doing :<br>
> > ./configure --prefix=/home/kc/mpich-install/ --enable-mpe<br>
> > --with-logging=SLOG CC=gcc CFLAGS=-g && make && make install<br>
> > It flashed an error messaage saying :<br>
> > onfigure: error: ./src/util/logging/SLOG does not exist.<br>
> Configure aborted<br>
><br>
> The --with-logging is for MPICH2's internal logging, not MPE's<br>
> logging.<br>
> As what you did below is fine is fine.<br>
> ><br>
> > After that, I tried :<br>
> > ./configure --prefix=/home/kc/mpich-install/ --enable-mpe CC=gcc<br>
> CFLAGS=-g<br>
> > && make && make install<br>
> > The installation was normal, when I tried compiling an<br>
> example<br>
> > program by doing :<br>
> > mpicc -mpilog -o sample sample.c<br>
> > cc1: error: unrecognized command line option "-mpilog"<br>
><br>
> Do "mpicc -mpe=mpilog -o sample sample.c" instead. For more details,<br>
> see "mpicc -mpe=help" and see mpich2/src/mpe2/README.<br>
><br>
> A.Chan<br>
><br>
> ><br>
> > Can anyone please tell me what needs to be done to use<br>
> the SLOG<br>
> > logging format?<br>
> ><br>
> > Thanks,<br>
> > Krishna Chaitanya K<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > In the middle of difficulty, lies opportunity<br>
> ><br>
><br>
><br>
><br>
><br>
> --<br>
> In the middle of difficulty, lies opportunity<br>
><br>
><br>
><br>
> --<br>
> In the middle of difficulty, lies opportunity<br>
><br>
><br>
><br>
> --<br>
> In the middle of difficulty, lies opportunity<br>
<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>In the middle of difficulty, lies opportunity