Okay, pushed https://bitbucket.org/petsc/petsc-dev/commits/1b382c0c8a0048fa000c4641e30980e1ca800f19
On Tue, Feb 12, 2013 at 11:37 AM, Barry Smith <bsmith at mcs.anl.gov> wrote: > > Stupid bitbucket doesn't let me respond to this. > > I think this is to handle the case where the vectors were obtained > without the appropriate block size so the routines called below cannot be > work properly. Perhaps the code should be changed so that the x and y bs > are only set if the jac->bs is a legitimate value and not when it is -1. > > Barry > > > Begin forwarded message: > > > From: Jed Brown <Bitbucket <commits-noreply at bitbucket.org>> > > Subject: Re: petsc/petsc-dev added -valgrind -debugger option to > petscmpiexec (commit 398f06830ac9d0920f8d4e4d0bac972857d520d4) > > Date: February 12, 2013 7:10:23 AM CST > > To: bsmith at mcs.anl.gov > > > > New comment on changeset: > > > > > https://bitbucket.org/petsc/petsc-dev/commits/398f06830ac9d0920f8d4e4d0bac972857d520d4#comment-146984 > > > > Jed Brown (jedbrown) said: > > > > What is this trying to achieve? In `runex19_4`, this results in changing > the block size from `4` to `-1`. Can we delete these lines or do we need to > set `jac->bs` in that case? > > > > -- > > This is an comment notification from bitbucket.org. > > You are receiving this because you are participating > > in a comment thread. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130212/4c8db49c/attachment-0001.html>
