[Bug 1319316] Re: gdb: Reading symbols from bin/mir_unit_tests...Segmentation fault (core dumped)

[Daniel van Vugt]

The bug occurs on trusty. Valgrind is telling me gdb is full of errors in:
    /usr/lib/x86_64-linux-gnu/libpython3.4m.so.1.0

but then:
==20810== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==20810==  Access not within mapped region at address 0xFFE801F98
==20810==    at 0x7137A9: ??? (in /usr/bin/gdb)


** Also affects: gdb (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: gdb (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1319316

Title:
  gdb: Reading symbols from bin/mir_unit_tests...Segmentation fault
  (core dumped)

Status in Mir:
  New
Status in “gdb” package in Ubuntu:
  Incomplete

Bug description:
  Something has changed recently in mir_unit_tests such that it is now
  undebuggable, causing gdb itself to crash:

  $ gdb bin/mir_unit_tests 
  ...
  Reading symbols from bin/mir_unit_tests...Segmentation fault (core dumped)

  I'm logging this as a Mir bug because it seems to be limited to
  mir_unit_tests. Maybe we can fix something as a workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1319316/+subscriptions