Bug#648052: metacity segfaults after todays update to wheezy

[S. G.]

Hi

>> If the problem is reproducible, please try to get a backtrace
> I will do my very best.

There is no package metacity-dbg hence no symbols. The backtrace result doesn't look
helpfully to me, see below.


sg at t500sg:~/bin$ gdb metacity
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 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".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/metacity...(no debugging symbols found)...done.
(gdb) set pagination 0
(gdb) run --replace
Starting program: /usr/bin/metacity --replace
[Thread debugging using libthread_db enabled]
Gtk-Message: Failed to load module "pk-gtk-module"
[New Thread 0x7fffeeaba700 (LWP 13658)]

Program received signal SIGSEGV, Segmentation fault.
0x0000000000458395 in ?? ()
(gdb) set logging on
Copying output to gdb.txt.
(gdb) thread apply all bt
Cannot find new threads: generic error
(gdb) bt
#0  0x0000000000458395 in ?? ()
Cannot access memory at address 0x7fffffffcda8
(gdb) bt full
#0  0x0000000000458395 in ?? ()
No symbol table info available.
Cannot access memory at address 0x7fffffffcda8


When running in gdb no segmentation fault is logged to /var/log/messages. 
Additionally I had to 'kill -KILL' metacity to get access to the console 
window again to issue command 'set logging on', etc.

Please give advice how to do better debugging. 


Sven