[petsc-users] PETSc fortran type check

Matthew Knepley knepley at gmail.com
Mon Aug 27 15:00:44 CDT 2012


On Mon, Aug 27, 2012 at 2:59 PM, Panruo Wu <pwu at mymail.mines.edu> wrote:

> Mat,
>
> Could you give some details on how I can find all the unchecked(checked)
> subroutines so that I can narrow down my search area when
> segfaults occur?
>

The right way to narrow this down is to use -start_in_debugger since you
will
immediately get the stack trace showing the offending method.

   Matt


> Thanks
> panruo
>
> On Mon, Aug 27, 2012 at 1:47 PM, Matthew Knepley <knepley at gmail.com>wrote:
>
>> On Mon, Aug 27, 2012 at 2:46 PM, Panruo Wu <pwu at mymail.mines.edu> wrote:
>>
>>> Hello PETSC developers and users,
>>>
>>> I read on link
>>>
>>> http://www.mcs.anl.gov/petsc/petsc-current/docs/manualpages/Sys/UsingFortran.html
>>>
>>> that approach 2 & 3 have some type check functionalities.  My question
>>> is which subroutines
>>> are type checked and which are not.  For example I guess that
>>> DMDACreate3d is checked
>>> (I'm using approach 3).
>>>
>>
>> The ones with interface declarations.
>>
>>    Matt
>>
>>
>>> Thanks and best wishes,
>>> Panruo Wu
>>>
>>
>>
>>
>> --
>> 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/20120827/49670fd6/attachment.html>


More information about the petsc-users mailing list