Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

ok, thanks. On Fri, Nov 24, 2023 at 10:16 PM Satish Balay wrote: > Do you really need this combination of pkgs? > > Matlab is distributed with ILP64 MKL - so it doesn't really work with > LP64 blas/lapack that most external packages require - i.e you can't > really use use matlab and other

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

Do you really need this combination of pkgs? Matlab is distributed with ILP64 MKL - so it doesn't really work with LP64 blas/lapack that most external packages require - i.e you can't really use use matlab and other external-packages. [also it might not work with complex] To get a successful

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

ok, thanks On Thu, Nov 23, 2023 at 10:49 PM Barry Smith wrote: > > Try option -start_in_debugger noxterm > > then when the debugger starts up > > c > > to continue the run. Then when the program crashes you can do > > bt > > to see exactly where the crash happens in SuperLU_DIST > > and > >

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

Try option -start_in_debugger noxterm then when the debugger starts up c to continue the run. Then when the program crashes you can do bt to see exactly where the crash happens in SuperLU_DIST and print "some variable name in the routine" to check if the variables there look

Re: [petsc-users] Segmentation Violation error using SuperLU_DIST in ex 19.c

Can you do a simple build with only superlu-dist and see if the error persists? ./configure PETSC_ARCH=linux-slu --with-cc=/usr/local/gcc11/bin/gcc --with-cxx=/usr/local/gcc11/bin/g++ --with-fc=gfortran --with-debugging=1 --with-scalar-type=complex --download-mpich --download-fblaslapack

Re: [petsc-users] Segmentation violation in DMPlexDistribute on MacOS

> --with-cc=gcc-mp-6 --with-cxx=g++-mp-6 Is it possible to use xcode compilers? I've seen wierd errors with mpich/openmpi and gcc on OSX - don't know how reliable they are on OSX. It would be a good test to check if the same error is reproduceable with them.. Satish On Tue, 6 Nov 2018,

Re: [petsc-users] Segmentation violation in DMPlexDistribute on MacOS

> On 6 Nov 2018, at 14:37, Maximilian Hartig via petsc-users > wrote: > > lldb returns the following: > > (lldb) process attach --pid 1082 > Process 1082 stopped > * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGSTOP > frame #0: 0x7fff5aa5c876

Re: [petsc-users] Segmentation violation

Hi Hong, You can find the matrices here: https://www.dropbox.com/s/ejpa9owkv8tjnwi/A.petsc?dl=0 https://www.dropbox.com/s/urjtxaezl0cv3om/B.petsc?dl=0 Changing the target value leads to the same error. What is strange is that this works without a problem on two other machines. But in my main

Re: [petsc-users] Segmentation violation

Santiago, The shift '-eps_target -2e-3+1.01i' is very close to the eigenvalues. What happens if you pick a target little away from your eigenvalues? I suspect mumps encounters a zero pivot during numerical factorization. There are options to handle it, but I need matrices A and B to investigate.

Re: [petsc-users] Segmentation violation

Yeah this doesn't look good for MUMPS but isn't for sure the problem either. The valgrind output should be sent to the MUMPS developers. Hong, Can you send this to the MUMPS developers and see what they say? Thanks Barry > On Oct 30, 2018, at 2:04 PM, Santiago

Re: [petsc-users] Segmentation violation

On Tue, Oct 30, 2018 at 1:18 PM Santiago Andres Triana via petsc-users < petsc-users@mcs.anl.gov> wrote: > Hi petsc-users, > > I am solving a generalized eigenvalue problem using ex7 in > $SLEPC_DIR/src/eps/examples/tutorials/. I provide the A and B matrices. > The program runs fine, with correct

Re: [petsc-users] Segmentation violation

Can you run the code on the "failing" machine using valgrind? https://www.mcs.anl.gov/petsc/documentation/faq.html#valgrind Barry > On Oct 30, 2018, at 12:10 PM, Santiago Andres Triana via petsc-users > wrote: > > Hi petsc-users, > > I am solving a generalized eigenvalue problem

Re: [petsc-users] Segmentation Violation in getting DMPlex coordinates

Hi Matt and Barry, Thanks for your quick response. After changing DMDAVecGetArrayF90 to VecGetArrayF90, everything works now. Thanks, Danyang On 18-04-28 01:38 PM, Smith, Barry F. wrote: Added runtime error checking for such incorrect calls in barry/dmda-calls-type-check On Apr 28,

Re: [petsc-users] Segmentation Violation in getting DMPlex coordinates

Added runtime error checking for such incorrect calls in barry/dmda-calls-type-check > On Apr 28, 2018, at 9:19 AM, Matthew Knepley wrote: > > On Sat, Apr 28, 2018 at 2:08 AM, Danyang Su wrote: > Hi All, > > I use DMPlex and need to get

Re: [petsc-users] Segmentation Violation in getting DMPlex coordinates

On Sat, Apr 28, 2018 at 2:08 AM, Danyang Su wrote: > Hi All, > > I use DMPlex and need to get coordinates back after distribution. However, > I always get segmentation violation in getting coords values in the > following codes if using multiple processors. If only one

[petsc-users] Segmentation Violation in getting DMPlex coordinates

Hi All, I use DMPlex and need to get coordinates back after distribution. However, I always get segmentation violation in getting coords values in the following codes if using multiple processors. If only one processor is used, it works fine. For each processors, the off value starts from 0

Re: [petsc-users] Segmentation violation issue when using MatSetVals in Fortran

Ah. Yes that definitely explains it. Weird that it seemed to work in some cases but I suppose the output would be total garbage. Anyways. Thank you both. Austin On Thu, Feb 2, 2017 at 1:32 PM, Matthew Knepley wrote: > On Thu, Feb 2, 2017 at 1:25 PM, Austin Herrema

Re: [petsc-users] Segmentation violation issue when using MatSetVals in Fortran

On Thu, Feb 2, 2017 at 1:25 PM, Austin Herrema wrote: > Hello all, > > I'm having a strange issue when using the MatSetVals function in Fortran. > The code is quite large, but relevant snippets of what I'm trying to do are > below. > > ! PETSc variable declaration > Mat

Re: [petsc-users] Segmentation violation issue when using MatSetVals in Fortran

> On Feb 2, 2017, at 10:25 PM, Austin Herrema wrote: > > Hello all, > > I'm having a strange issue when using the MatSetVals function in Fortran. The > code is quite large, but relevant snippets of what I'm trying to do are below. > > ! PETSc variable declaration >

[petsc-users] Segmentation violation issue when using MatSetVals in Fortran

Hello all, I'm having a strange issue when using the MatSetVals function in Fortran. The code is quite large, but relevant snippets of what I'm trying to do are below. ! PETSc variable declaration Mat LHS PetscErrorCode ier PetscInt idx1(nsd*nsd*nshl*nshl), idx2(nsd*nsd*nshl*nshl)

Re: [petsc-users] Segmentation Violation for SNES ex12

On Sun, Jan 11, 2015 at 10:05 PM, Justin Chang jychan...@gmail.com wrote: Hi all, Our research group recently got access to a relatively new HPC cluster (with SLURM scheduler) and I am trying to run some test examples with it on multiple processors. When I run SNES ex12 serially it works.

[petsc-users] Segmentation Violation for SNES ex12

Hi all, Our research group recently got access to a relatively new HPC cluster (with SLURM scheduler) and I am trying to run some test examples with it on multiple processors. When I run SNES ex12 serially it works. However when i run it on two processes, I get the following error: [0]PETSC

[petsc-users] Segmentation Violation

Dear all, I have some issue with my code using petsc. The exact same code runs fine on a linux box with ifort. Is that still be a possible memory corruption? I have some issue with getting valgrind working on 10.7. Is there any better way to debug this? Thanks. Here is the error message I got for

[petsc-users] Segmentation Violation

On Fri, Aug 10, 2012 at 8:22 PM, Peter Zhoujie Lu lzj at umich.edu wrote: Dear all, I have some issue with my code using petsc. The exact same code runs fine on a linux box with ifort. Is that still be a possible memory corruption? I have some issue with getting valgrind working on 10.7. Is

[petsc-users] Segmentation Violation, is this a bug?

Hi, Petsc Team, Recently I encounter a weird problem for segmentation violation. I wrote a simple test code to describe it. Here the line pp = sk[j+1][i].p; causes segmentation violation trouble when I try to invoke values of ghost points in j direction. If I change it into pp =

[petsc-users] Segmentation Violation in a very simple fortran code

Hi, I'm stuck with an implementation of a 3D Poisson solver with PETSc in fortran90. I was getting strange Segmentation Violation and after some debugging I realized that the the problem was in the vector created with DACreateGlobalVector() So I've written a simple code:

[petsc-users] Segmentation Violation in a very simple fortran code

To: petsc-users at mcs.anl.gov Subject: [petsc-users] Segmentation Violation in a very simple fortran code Hi, I'm stuck with an implementation of a 3D Poisson solver with PETSc in fortran90. I was getting strange Segmentation Violation and after some debugging I realized that the the problem

[petsc-users] Segmentation Violation in a very simple fortran code

The VecView() has no 'err' argument. Matt On Thu, Jun 17, 2010 at 11:19 PM, Valerio Grazioso graziosov at me.queensu.cawrote: Hi, I'm stuck with an implementation of a 3D Poisson solver with PETSc in fortran90. I was getting strange Segmentation Violation and after some debugging I

[petsc-users] Segmentation Violation in a very simple fortran code

Ok... but adding it I get in the same position a different error: [0]PETSC ERROR: - Error Message [1]PETSC ERROR: [0]PETSC ERROR: Invalid argument! [0]PETSC ERROR: Wrong type of object: Parameter # 1! [0]PETSC ERROR:

[petsc-users] Segmentation Violation in a very simple fortran code

?mcmodel=medium to the compile line and see that helps. Logan From: petsc-users-bounces at mcs.anl.gov [mailto:petsc-users-bounces at mcs.anl.gov] On Behalf Of Valerio Grazioso Sent: Thursday, June 17, 2010 11:20 PM To: petsc-users at mcs.anl.gov Subject: [petsc-users] Segmentation

[petsc-users] Segmentation Violation in a very simple fortran code

This is obviously not the whole code because you are calling PetscViewerDestroy() somewhere with a bad viewer. Please check the return codes of all PETSc calls. THanks, Matt On Thu, Jun 17, 2010 at 11:43 PM, Valerio Grazioso graziosov at me.queensu.cawrote: Ok... but adding it I get in

[petsc-users] Segmentation Violation in a very simple fortran code

What about trying this flag -heap-arrays 1024 ? Logan From: petsc-users-bounces at mcs.anl.gov [mailto:petsc-users-boun...@mcs.anl.gov] On Behalf Of Valerio Grazioso Sent: Thursday, June 17, 2010 11:58 PM To: PETSc users list Subject: Re: [petsc-users] Segmentation Violation in a very simple

[petsc-users] Segmentation Violation in a very simple fortran code

Of Valerio Grazioso Sent: Thursday, June 17, 2010 11:58 PM To: PETSc users list Subject: Re: [petsc-users] Segmentation Violation in a very simple fortran code I am new to PETSc too. OpenMPI and Intel compiler (ifort). Unfortunately -mcmodel=medium doesn't help. Thanks anyway Valerio

[petsc-users] Segmentation Violation in a very simple fortran code

call PetscFinalize(PETSC_NULL_CHARACTER,err) PetscFinalize() does not take a string argument, you should have call PetscFinalize(err) On Jun 17, 2010, at 11:19 PM, Valerio Grazioso wrote: Hi, I'm stuck with an implementation of a 3D Poisson solver with PETSc in fortran90. I was

[petsc-users] Segmentation Violation in a very simple fortran code

Hi Matt, you were right, there was a stupid error with a missing argument in the VecView() routine. Thanks a lot Valerio On 2010-06-18, at 8:32 AM, Matthew Knepley wrote: I suspect that a) Not all arguments are correct, Fortran does not checking b) Some object was not created