Reported by Denis D, Jul 16, 2015
dear all, i experience a segmentation fault error in Parpack 3.1.4 compiled with Scalapack 2.0.2. I don't know whether this is an issue of Parpack, Scalapack or a mistake in a driving program. What I know is that the issue disappears in the head version of Scalapack. I get the SEGV error when using Parpack inside a FEM code, but a more straight forward way to reproduce the problem is: 1. download a simple program from here http://forge.scilab.org/index.php/p/arpack-ng/issues/1480/ 2. compile and run it even with 1 processor. Expected result: pass Actual result: Process 12397 stopped * thread #1: tid = 0xb446d, 0x0000000115765ccc libscalapack.dylib`dgamx2d_ + 64, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) frame #0: 0x0000000115765ccc libscalapack.dylib`dgamx2d_ + 64 libscalapack.dylib`dgamx2d_: -> 0x115765ccc <+64>: movq (%rax,%rdi,8), %r14 0x115765cd0 <+68>: movb (%rdx), %bl 0x115765cd2 <+70>: movb %bl, %al 0x115765cd4 <+72>: addb $-0x41, %al (lldb) bt * thread #1: tid = 0xb446d, 0x0000000115765ccc libscalapack.dylib`dgamx2d_ + 64, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0) * frame #0: 0x0000000115765ccc libscalapack.dylib`dgamx2d_ + 64 frame #1: 0x00000001158f9157 libscalapack.dylib`pdlamch_ + 167 frame #2: 0x000000011601d75b libparpack.2.dylib`pdsaupd_ + 2267 frame #3: 0x0000000100027aac dvr_parpack`pdsaupd(n=256, nev=10, Evals=0x000000011f311fa0, Evecs=0x0000000120803200) + 1100 at dvr_parpack.cc:308 frame #4: 0x0000000100026621 dvr_parpack`main(nr_arguments=2, arguments=0x00007fff5fbffa60) + 449 at dvr_parpack.cc:142 frame #5: 0x00007fff92e545c9 libdyld.dylib`start + 1 I would appreciate if somebody at least try to compile the driver program above to see if the issue is there on his/her system. p.s. i also reported this issue in Scalapack forum, but did not have any replies there so far http://icl.cs.utk.edu/lapack-forum/viewtopic.php?f=13&t=4676& p=11434#p11434
Sign in to reply to this comment.