Analysing Core - Process has crashed but stack not showing any errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • afrah
    New Member
    • Jul 2010
    • 12

    Analysing Core - Process has crashed but stack not showing any errors

    I am getting a core dump and in the core dump it says New Process 19143 etc before displaying the stack.
    the stack doesnot show any errors but my process has crashed.
    I am guessing the core is not showing complete info as there r some new processes created which cud hav crashed.
    Can any1 help me with this.
  • ashitpro
    Recognized Expert Contributor
    • Aug 2007
    • 542

    #2
    Whats the size given for the ulimit?
    Try using this command
    'ulimit -C unlimited'

    Whenever dump is generated, it is generated for particular process. So, even if you create multiple processes, whatever is in dump; should give you all information related to crash.

    If that doesn't work then go for gdb or valgrind.

    Comment

    • afrah
      New Member
      • Jul 2010
      • 12

      #3
      Hi
      Thanks for the reply i already hav an unlimited core size.
      I am already using gdb.
      But its not of much use.

      Comment

      • ashitpro
        Recognized Expert Contributor
        • Aug 2007
        • 542

        #4
        whats wrong with gdb?
        Ultimately you are supposed to analyze the coredump with gdb only.

        Using gdb, when it crashes, what out output does it give if 'bt' command is given to gdb?

        Comment

        Working...