[petsc-dev] d9ca1df42eda25bc875149d6d493aad6e204c9ff

Matthew Knepley knepley at gmail.com
Wed Feb 4 15:47:16 CST 2015

On Wed, Feb 4, 2015 at 3:45 PM, Mark Adams <mfadams at lbl.gov> wrote:

> This commit seems to have caused my MatShell code to break:
> [22]PETSC ERROR: Object is in wrong state
> [22]PETSC ERROR:  Vec is locked read only, argument # 1

Is your MatShell code using VecGetArray() when it should be using



> This seems to be the problem (Barry):
> 16:40 (5edff71...)|BISECTING ~/Codes/petsc$ git bisect bad
> Bisecting: 0 revisions left to test after this (roughly 0 steps)
> [d9ca1df42eda25bc875149d6d493aad6e204c9ff] Added VecLockPush() and
> VecLockPop() to make vector read only Used VecLockPush() and VecLockPop()
> in a couple of key locations; PCApply(), KSPSolve(), MatMult() Fixed many
> uses of VecGetArray() to VecGetArrayRead() Added VecGet/RestoreArrayPair()
> for commonly occuring pattern Added const to many locations driven by use
> of VecGetArrayRead()

What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150204/0f1ed324/attachment.html>

More information about the petsc-dev mailing list