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

[Andreas Pokorny]

Bug seems to be unrelated to the gdb version it also happens for
7.7-0ubuntu3

and valgrind says:
Stack overflow in thread 1: can't grow stack to 0xffe801f48
==13825== 
==13825== Process terminating with default action of signal 11 (SIGSEGV)
==13825==  Access not within mapped region at address 0xFFE801F48
==13825==    at 0x713722: ??? (in /usr/bin/gdb)
==13825==  If you believe this happened as a result of a stack
==13825==  overflow in your program's main thread (unlikely but
==13825==  possible), you can try to increase the size of the
==13825==  main thread stack using the --main-stacksize= flag.
==13825==  The main thread stack size used in this run was 8388608.
==13825== Stack overflow in thread 1: can't grow stack to 0xffe801f40
==13825== 
==13825== Process terminating with default action of signal 11 (SIGSEGV)
==13825==  Access not within mapped region at address 0xFFE801F40

-- 
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