Bug#766732: Attempting (failing) to load debugging symbols for glib-2.0-0

[Brian Drummond]

Backtrace revealed missing debug info in glib, viz...
Thread 5 (Thread 0x7fffe5d4e700 (LWP 3843)):
#0  0x00007ffff3c760ed in poll () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x00007ffff4c52ee4 in ?? ()
from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
... etc

So I thought I needed to install the debug version of libglib2.0-0
sudo apt-get -t testing install libglib2.0-0-dbg
(looks OK)

And try again...

gdb nautilus
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
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 nautilus...Reading symbols
from /usr/lib/debug//usr/bin/nautilus...done.
done.
(gdb) run
Starting program: /usr/bin/nautilus 
BFD: /usr/lib/debug/.build-id/f4/bb3ff29b5a72f4c60cc4f76854a1bb47a3bc78.debug: unable to initialize decompress status for section .zdebug_aranges
warning: File
"/usr/lib/debug/.build-id/f4/bb3ff29b5a72f4c60cc4f76854a1bb47a3bc78.debug" has no build-id, file skipped
BFD: /usr/lib/debug/.build-id/c0/753208ea46400cd99ae9e1591b4767358d1679.debug: unable to initialize decompress status for section .zdebug_aranges
warning: File
"/usr/lib/debug/.build-id/c0/753208ea46400cd99ae9e1591b4767358d1679.debug" has no build-id, file skipped
(and several more)
[New Thread 0x7fffedaf2700 (LWP 3989)]

Am I missing something or is there a problem with the debug package?
Sorry about the noise on this bug report, I seem to be struggling.

- Brian