Couchbase Server

analyze_core fails on truncated core

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 1.7 GA, 1.7.1
  • Fix Version/s: .next
  • Component/s: tools
  • Security Level: Public
  • Labels:
    None

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Farshid Ghods added a comment -
Aliaksey,

can you please take a look and see if this is an easy fix for 2.0 GA
Show
Farshid Ghods added a comment - Aliaksey, can you please take a look and see if this is an easy fix for 2.0 GA
Hide
Permalink
Peter Wansch added a comment -
Jin, is this something you can try out?
Show
Peter Wansch added a comment - Jin, is this something you can try out?
Hide
Permalink
Jin Lim 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 Lim 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
Permalink
Jin Lim 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 Lim 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 Lim
    Reporter:
    Keith Batten
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: