Comment 1 for bug 1008593

Reported by louisb in the forums:

I also get a segfault on bluez. here is the back trace:

Program received signal SIGSEGV, Segmentation fault.
0x4015b014 in ?? () from /usr/lib/libcap-ng.so.0
(gdb) bt
#0 0x4015b014 in ?? () from /usr/lib/libcap-ng.so.0
#1 0x400121c0 in __tls_get_addr () from /lib/arm-linux-gnueabihf/ld-linux.so.3
#2 0x4015b220 in capng_clear () from /usr/lib/libcap-ng.so.0
#3 0x4015b220 in capng_clear () from /usr/lib/libcap-ng.so.0
#4 0x2a00c618 in main (argc=1073782848, argv=0xb) at src/main.c:451

running readelf -A /usr/lib/libcap-ng.so.0 using readelf -A I get:

raspbian@pisces:/etc/init.d$ readelf -A /usr/lib/libcap-ng.so.0.0.0
Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "6"
  Tag_CPU_arch: v6
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-1
  Tag_FP_arch: VFPv2
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_align_preserved: 8-byte, except leaf SP
  Tag_ABI_enum_size: int
  Tag_ABI_HardFP_use: SP and DP
  Tag_ABI_VFP_args: VFP registers
  Tag_ABI_optimization_goals: Aggressive Speed
  Tag_DIV_use: Not allowed

should it really have Tag_ABI_optimization_goals: Aggressive Speed?