[petsc-users] Segmentation error when calling PetscBarrier

[Matthew Knepley]

On Mon, Jan 4, 2016 at 7:41 PM, TAY wee-beng <zonexo at gmail.com> wrote:

> Hi Matt,
>
> In that case, what would be a good or accurate way to debug the MPI code?
> I'm trying to determine where the fault lies.
>

Is there a problem with -start_in_debugger? Also valgrind
--trace-children=yes is great.

  Thanks,

    Matt


> Thank you
>
> Yours sincerely,
>
> TAY wee-beng
>
> On 5/1/2016 9:31 AM, Matthew Knepley wrote:
>
> On Mon, Jan 4, 2016 at 7:28 PM, TAY wee-beng <zonexo at gmail.com> wrote:
>
>> Hi,
>>
>> I am trying to debug my CFD Fortran MPI code. I tried to add:
>>
>> call PetscBarrier(PETSC_NULL_OBJECT); if (myid==0) print *, "xx"
>>
>> to do a rough check on where the error is. xx is a different number for
>> each line.
>>
>> I found that whenever I add this line, the code aborts with segmentation
>> error.
>>
>> I am using the Intel compiler. Is there any error with my usage?
>
>
> I don't think this makes sense since it will try to pull a communicator
> out of the NULL_OBJECT.
>
>    Matt
>
>
>>
>> --
>> Thank you
>>
>> Yours sincerely,
>>
>> TAY wee-beng
>>
>>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>
>
>


-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20160104/898ec9f4/attachment.html>