fvMeshGeometry: Dump core if phi() is called for a non-moving mesh to help trace problem
This commit is contained in:
parent
4c9dc30ed4
commit
08cff2ac41
1 changed files with 2 additions and 2 deletions
|
|
@ -441,7 +441,7 @@ const surfaceScalarField& fvMesh::phi() const
|
|||
{
|
||||
FatalErrorIn("fvMesh::phi()")
|
||||
<< "mesh flux field does not exist, is the mesh actually moving?"
|
||||
<< exit(FatalError);
|
||||
<< abort(FatalError);
|
||||
}
|
||||
|
||||
// Set zero current time
|
||||
|
|
@ -461,7 +461,7 @@ surfaceScalarField& fvMesh::setPhi()
|
|||
{
|
||||
FatalErrorIn("fvMesh::setPhi()")
|
||||
<< "mesh flux field does not exist, is the mesh actually moving?"
|
||||
<< exit(FatalError);
|
||||
<< abort(FatalError);
|
||||
}
|
||||
|
||||
return *phiPtr_;
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue