Creation of core.* file in current running directory

Member Site Forums Rosetta 3 Rosetta 3 – General Creation of core.* file in current running directory

  • This topic has 2 replies, 2 voices, and was last updated 13 years ago by Anonymous.
Viewing 2 reply threads
  • Author
    Posts
    • #1110
      Anonymous

        Good afternoon,

        I’m using Rosetta as a library inside my own code and I’m running several instances of my programs on a cluster. It happens that, sometimes, a file named core.* is created in the directory where the programs are launched where * is a number (e.g. 1041, 15897, etc.). This file can weight up to 2GB but its size varies.

        Can anyone explain this behavior, tell me if it’s normal and give me some clues to avoid the creation of this file?

        Thank you in advance for your help

      • #6366
        Anonymous

          These are core dumps, http://en.wikipedia.org/wiki/Core_dump. Those are bad. Basically it means your code crashed. If you don’t know how to use a core dump (I certainly don’t), just delete them, and try to figure out from the log file why the code is crashing. Do you have Rosetta’s tracer output being printed to file?

          In my experience, Rosetta never core dumps – segfaults, yes, but not core dumps. I think it’s an OS setting that causes it to generate core dumps instead of just silently deleting them, or something to do with your program.

        • #6371
          Anonymous

            In my experience, Rosetta never core dumps – segfaults, yes, but not core dumps. I think it’s an OS setting that causes it to generate core dumps instead of just silently deleting them, or something to do with your program.

            You’re probably right because this doesn’t seem to happen when my code crashes. I’m just going to delete them.

            Thanks for your help

        Viewing 2 reply threads
        • You must be logged in to reply to this topic.