Comment 7 for bug 107253

OK, I've installed the dbgsym packages on my feisty machine (I was wanting to install them on the dapper one at work), and there I get exactly the same kind of behaviour as hggdh has: an endless loop writing to nautilus-debug-log.txt, where that file begins

0x7601b0 2007/04/17 19:57:38.9127 (GLog): g_filename_display_basename: assertion `filename != NULL' failed
0x7601b0 2007/04/17 19:57:38.9132 (GLog): g_filename_display_basename: assertion `filename != NULL' failed
0x7601b0 2007/04/17 19:57:38.9165 (GLog): nautilus_information_panel_set_uri: assertion `initial_title != NULL' failed
0x7601b0 2007/04/17 19:57:39.0228 (GLog): g_filename_display_basename: assertion `filename != NULL' failed
0x7601b0 2007/04/17 19:57:39.0287 (GLog): g_filename_display_basename: assertion `filename != NULL' failed
0x7601b0 2007/04/17 19:57:39.0289 (GLog): g_filename_display_basename: assertion `filename != NULL' failed
0x7601b0 2007/04/17 19:57:39.0290 (USER): debug log dumped due to signal 11
[repeated endlessly]

Attaching gdb to an already-wedged nautilus said

0x00002b17527abc2f in _IO_file_xsputn () from /lib/libc.so.6
(gdb) continue
Continuing.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47379268483952 (LWP 32272)]
compare_by_display_name (file_1=0x12a2b30, file_2=0x12a2c10) at nautilus-file.c:1829
1829 nautilus-file.c: No such file or directory.
        in nautilus-file.c
(gdb) bt
#0 compare_by_display_name (file_1=0x12a2b30, file_2=0x12a2c10) at nautilus-file.c:1829
#1 0x00000000004c8dbe in nautilus_file_compare_for_sort (file_1=0x12a2b30, file_2=0x12a2c10, sort_type=NAUTILUS_FILE_SORT_BY_DISPLAY_NAME, directories_first=<value optimized out>, reversed=0) at nautilus-file.c:2182

I'm wondering whether I should trace this through from the other direction: what's the name of the tool that appears when you press alt-f2, and which package provides it?