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

[Daniel van Vugt]

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.

[Daniel van Vugt (vanvugt)]

Before you ask, yes I have tried uploading crash reports but the upload silently fails :/

[Alan Griffiths (alan-griffiths)]

I can't reproduce from the instructions given:
$ gdb bin/mir_unit_tests
GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from bin/mir_unit_tests...done.
(gdb)

[Daniel van Vugt (vanvugt)]

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)

[Andreas Pokorny (andreas-pokorny)]

Could not upload a crash report either - I am not also affected after applying updates from utopic:
# gdb --version
GNU gdb (Ubuntu 7.7.1-0ubuntu1) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
...

[Andreas Pokorny (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

[Andreas Pokorny (andreas-pokorny)]

I made some further attempts with older versions of "mir_unit_tests". Binaries built with g++-4.8.2-1ubuntu6 or maybe even before that work while all binaries built with g++-4.8.2-4ubuntu1 have the issue.

[Matthias Klose (doko)]

no feedback, closing the gdb task as invalid

[Launchpad Janitor (janitor)]

[Expired for Mir because there has been no activity for 60 days.]