Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
fleur
fleur
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • fleur
  • fleurfleur
  • Issues
  • #413

Closed
Open
Opened Mar 21, 2020 by Matthias Redies@rediesDeveloper

Extend `-trace` option with a coredump

On must linux machines programs will cause a coredump if there is a memory problem. Our judft_error call don't do this. It would be nice if we could somehow trigger this. (I have seen some examples for C/C++). An option similar to -trace would be nice.

These core dumps can be loaded into a debugger (gdb or totalview) and then one can see the whole program state rather than just the position.

Edited Mar 21, 2020 by Matthias Redies
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: fleur/fleur#413