Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 1.7.0, 1.7.1
    • Fix Version/s: bug-backlog
    • Component/s: tools
    • Security Level: Public
    • Labels:
      None
    • Triage:
      Untriaged

      Description

      Running analyze_core against a core dump get the following error:

      BFD: Warning: /tmp/backup/core.memcached.32750 is truncated: expected core file size >= 1891549184, found: 1891545088.
      Failed to determine the binary name from the corefile

      Note that if you run gdb directly against the core with the binary name we do get data back.

      No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

        Hide
        farshid Farshid Ghods (Inactive) added a comment -

        Aliaksey,

        can you please take a look and see if this is an easy fix for 2.0 GA

        Show
        farshid Farshid Ghods (Inactive) added a comment - Aliaksey, can you please take a look and see if this is an easy fix for 2.0 GA
        Hide
        peter peter added a comment -

        Jin, is this something you can try out?

        Show
        peter peter added a comment - Jin, is this something you can try out?
        Hide
        jin Jin Lim (Inactive) added a comment -

        Why not Assuming this is a in-house tool (script), I will try if I can quickly learn and determine a fix for it.
        Thanks!

        Show
        jin Jin Lim (Inactive) added a comment - Why not Assuming this is a in-house tool (script), I will try if I can quickly learn and determine a fix for it. Thanks!
        Hide
        jin Jin Lim (Inactive) added a comment -

        Without the platform information for where this issue originally occurred, I was only able to reproduce a similar symptom by infusing a false SIGSEGV and the filesystem is fairly full. I believe it must have been an environment issue (i.e. disk space, etc) of the testing platform.

        Close the bug for now. Will open a new bug if a similar symtom occurs or gets reported during our testing.

        Show
        jin Jin Lim (Inactive) added a comment - Without the platform information for where this issue originally occurred, I was only able to reproduce a similar symptom by infusing a false SIGSEGV and the filesystem is fairly full. I believe it must have been an environment issue (i.e. disk space, etc) of the testing platform. Close the bug for now. Will open a new bug if a similar symtom occurs or gets reported during our testing.

          People

          • Assignee:
            jin Jin Lim (Inactive)
            Reporter:
            keith Keith Batten (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes