On Fri, Oct 7, 2016 at 9:04 AM, Satish Balay <ba...@mcs.anl.gov> wrote:
> On Fri, 7 Oct 2016, Anton Popov wrote: > > > Hi guys, > > > > are there any news about fixing buggy behavior of SuperLU_DIST, exactly > what > > is described here: > > > > https://urldefense.proofpoint.com/v2/url?u=http-3A__lists. > mcs.anl.gov_pipermail_petsc-2Dusers_2015-2DAugust_026802.html&d=CwIBAg&c= > 54IZrppPQZKX9mLzcGdPfFD1hxrcB__aEkJFOKJFd00&r=DUUt3SRGI0_ > JgtNaS3udV68GRkgV4ts7XKfj2opmiCY&m=RwruX6ckX0t9H89Z6LXKBfJBOAM2vG > 1sQHw2tIsSQtA&s=bbB62oGLm582JebVs8xsUej_OX0eUwibAKsRRWKafos&e= ? > > > > I'm using 3.7.4 and still get SEGV in pdgssvx routine. Everything works > fine > > with 3.5.4. > > > > Do I still have to stick to maint branch, and what are the chances for > these > > fixes to be included in 3.7.5? > > 3.7.4. is off maint branch [as of a week ago]. So if you are seeing > issues with it - its best to debug and figure out the cause. > This bug is indeed inside of superlu_dist, and we started having this issue from PETSc-3.6.x. I think superlu_dist developers should have fixed this bug. We forgot to update superlu_dist?? This is not a thing users could debug and fix. I have many people in INL suffering from this issue, and they have to stay with PETSc-3.5.4 to use superlu_dist. Fande > > Satish >