gdb mir_demo_server_shell takes a very long time to start (over a minute)
Bug #1352772 reported by
Daniel van Vugt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Expired
|
Medium
|
Unassigned |
Bug Description
I can't run mir_demo_
$ sudo gdb bin/mir_
...
Reading symbols from bin/mir_
(gdb) run
Starting program: /home/dan/
Got object file from memory but can't read symbols: File truncated.
Update: It starts eventually! You just have to wait a minute or two. So that's still a bug.
summary: |
- Can't run mir_demo_server_shell under gdb any more + gdb mir_demo_server_shell takes a very long time to start (over a + minute) |
description: | updated |
Changed in mir: | |
importance: | Undecided → Medium |
To post a comment you must log in.
This happens when using gdb on an executable that is built without optimizations (the default for our builds). A workaround is to build with optimization flags, for instance enabling the debian build flags (cmake -Duse_debflags= true).
No idea why this is happening but gdb seems to be spending a lot of time in:
#0 0x00000000006a4b70 in bfd_seek () get_section_ contents () get_synthetic_ symtab ()
#1 0x00000000006aa540 in _bfd_generic_
#2 0x00000000006be86b in ?? ()
#3 0x00000000006d5184 in _bfd_elf_
#4 0x00000000006be32a in ?? ()
#5 0x0000000000506d41 in ?? ()
#6 0x000000000057a829 in ?? ()
#7 0x000000000057a3f8 in ?? ()
#8 0x0000000000679049 in solib_read_symbols ()
#9 0x00000000006794e8 in solib_add ()
#10 0x0000000000679973 in handle_solib_event ()
I don't think this is bug is caused by Mir, probably a gdb or gcc/ld bug.