Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 380
    • Issues 380
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1537

Closed
Open
Created Jan 02, 2020 by Vaggelis Papoutsis@vaggelispDeveloper

BUG: Wrong FatalIOError message in displacementMethod and optMeshMovement

Summary

The core of the FatalIOError message, including the table of contents of the base class, is not printed by displacementMethod::New and optMeshMovement::New due to exiting the FatalIOError call with exit(FatalError) instead of exit(FatalIOError).

Steps to reproduce

Enter a non-valid displacementMethod (in dynamicMeshDict) or meshMovement type (in optimisationDict) in any of the tutorials under $FOAM_TUTORIALS/incompressible/adjointOptimisationFoam/shapeOptimisation.

What is the current bug behaviour?

No error message content is printed, only the Fatal Error line.

What is the expected correct behavior?

The full FatalError message, including the toc of the base class should be printed.

Assignee
Assign to
Time tracking