<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
Hi Barry,<br>
I have moved to main and rebuilt the PETSc libraries etc. Right
now I am having trouble just getting my source code to compile.
Plenty of subroutines with PETSc calls compile but a few are
throwing errors and killing my compile. I suspect there will be more
but if I can figure these hopefully I can debug the ones that will
follow.<br>
-sanjay<br>
<blockquote>Error: There is no specific subroutine for the generic
'matmpibaijsetpreallocation' at (1)<br>
upremas.F:68:72:<br>
<br>
68 | & ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'matseqbaijsetpreallocation' at (1)<br>
upremas.F:74:72:<br>
<br>
74 | & ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'matmpiaijsetpreallocation' at (1)<br>
upremas.F:77:72:<br>
<br>
77 | & ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'matseqaijsetpreallocation' at (1)<br>
<br>
parkv.F:58:25:<br>
<br>
58 | PetscViewer Y_view<br>
| 1<br>
Error: Type name 'tpetscviewer' at (1) is ambiguous<br>
parkv.F:69:9:<br>
<br>
69 | endif<br>
| 1<br>
Error: Expecting END SUBROUTINE statement at (1)<br>
parkv.F:72:9:<br>
<br>
72 | endif<br>
| 1<br>
Error: Expecting END SUBROUTINE statement at (1)<br>
parkv.F:91:66:<br>
<br>
91 | call
PetscViewerASCIIOpen(PETSC_COMM_WORLD,"yvec.m",Y_view,<br>
|
1<br>
Error: Symbol 'y_view' at (1) has no IMPLICIT type; did you mean
'yvec'?<br>
parkv.F:65:72:<br>
<br>
65 | call VecCreate (PETSC_COMM_WORLD, xvec,
ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic 'veccreate'
at (1)<br>
parkv.F:67:72:<br>
<br>
67 | call VecSetFromOptions(xvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecsetfromoptions' at (1)<br>
parkv.F:68:72:<br>
<br>
68 | call VecDuplicate (xvec, yvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecduplicate' at (1)<br>
parkv.F:71:72:<br>
<br>
71 | call VecDuplicate (xvec, yvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecduplicate' at (1)<br>
parkv.F:85:72:<br>
<br>
85 | call VecAssemblyBegin(xvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecassemblybegin' at (1)<br>
parkv.F:86:72:<br>
<br>
86 | call VecAssemblyEnd (xvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecassemblyend' at (1)<br>
parkv.F:88:72:<br>
<br>
88 | call MatMult (Kmat, xvec, yvec, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic 'matmult'
at (1)<br>
parkv.F:101:72:<br>
<br>
101 | call VecGetOwnershipRange(yvec, starti, endi, ierr)<br>
|
1<br>
Error: There is no specific subroutine for the generic
'vecgetownershiprange' at (1)<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">-
</pre>
<div class="moz-cite-prefix">On 3/21/25 7:17 AM, Barry Smith wrote:<br>
</div>
<blockquote type="cite"
cite="mid:25C4C2FE-0915-4331-A0E2-540FC513BD6C@petsc.dev">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div><br>
</div>
I have just pushed a major update to the Fortran interface to
the main PETSc git branch. Could you please try to work with main
(to become release in a couple of weeks) with your Fortran code as
we debug the problem? This will save you a lot of work and
hopefully make the debugging more straightforward.
<div><br>
</div>
<div> You can send the same output with the debugger if it
crashes in the main branch and I can try to track down what is
going wrong.</div>
<div><br>
</div>
<div> Barry</div>
<div><br>
<div><br>
</div>
<div> <br id="lineBreakAtBeginningOfMessage">
<div><br>
<blockquote type="cite">
<div>On Mar 21, 2025, at 12:37 AM, Sanjay Govindjee via
petsc-users <a class="moz-txt-link-rfc2396E" href="mailto:petsc-users@mcs.anl.gov"><petsc-users@mcs.anl.gov></a> wrote:</div>
<br class="Apple-interchange-newline">
<div>
<meta http-equiv="content-type"
content="text/html; charset=UTF-8">
<div> I am trying to upgrade my code to PETSc 3.22.4
(the code was last updated to 3.19.4 or perhaps
3.18.1, I've lost track). I've been using this code
with PETSc for over 20 years.<br>
<br>
To get my code to compile and link during this update,
I only need to make two changes; one was to use
PetscViewerPushFormat instead of PetscViewerSetFormat
and the other was to use PETSC_NULL_INTEGER_ARRAY in a
spot or two.<br>
<br>
When I run the code however, I am getting an error
very early on during a call to MatCreate near the
beginning of the code. The screen output says:<br>
<blockquote>[3]PETSC ERROR: matcreate_() at
/Users/sg/petsc-3.22.4/gnug/src/mat/utils/ftn-auto/gcreatef.c:101
Cannot create PETSC_NULL_XXX object<br>
[0]PETSC ERROR: matcreate_() at
/Users/sg/petsc-3.22.4/gnug/src/mat/utils/ftn-auto/gcreatef.c:101
Cannot create PETSC_NULL_XXX object<br>
[1]PETSC ERROR: matcreate_() at
/Users/sg/petsc-3.22.4/gnug/src/mat/utils/ftn-auto/gcreatef.c:101
Cannot create PETSC_NULL_XXX object<br>
[2]PETSC ERROR: matcreate_() at
/Users/sg/petsc-3.22.4/gnug/src/mat/utils/ftn-auto/gcreatef.c:101
Cannot create PETSC_NULL_XXX object<br>
</blockquote>
I have a 4 processor run going. I am running with
-on_error_attach_debugger but the debugger is giving
me cryptic (at least to me) output (the same for all 4
processes modulo the PID). Stack traces seem to be
unavailable :(<br>
<blockquote>lldb -p 71963 <br>
(lldb) process attach --pid 71963<br>
Process 71963 stopped<br>
* thread #1, queue = 'com.apple.main-thread', stop
reason = signal SIGSTOP<br>
frame #0: 0x00007fff69d92746
libsystem_kernel.dylib`__semwait_signal + 10<br>
libsystem_kernel.dylib`__semwait_signal:<br>
-> 0x7fff69d92746 <+10>: jae
0x7fff69d92750 ; <+20><br>
0x7fff69d92748 <+12>: movq %rax, %rdi<br>
0x7fff69d9274b <+15>: jmp
0x7fff69d9121d ; cerror<br>
0x7fff69d92750 <+20>: retq <br>
Target 0: (feap) stopped.<br>
<br>
Executable module set to
"/Users/sg/Feap/ver87/parfeap/feap".<br>
Architecture set to: x86_64h-apple-macosx-.<br>
</blockquote>
Does anyone have any hints as to what may be going
on? Note the program starts normally and i can do
stuff with the interactive interface for the code --
even plotting the mesh etc. so I believe the input
data has been read in correctly. The crash only
occurs when I initiate the formation of the matrix.<br>
<br>
I am attaching the
/Users/sg/petsc-3.22.4/gnug/src/mat/utils/ftn-auto/gcreatef.c
file in case that offers some insight.<br>
<br>
Note, I have been <br>
-sanjay<br>
<pre class="moz-signature" cols="72">--
</pre>
</div>
<span id="cid:AC0FE96A-AADA-47D9-9FBE-0432829B6ECA"><gcreatef.c></span></div>
</blockquote>
</div>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>