Xffm crashes when expanding my home dir.

[Jonathan Gardner]

On Thursday, the 09th day of January, in the year of our Lord 2003, at
08:51 AM the esteemed person of letters, edscott wilson garcia quoth:

EWG> > I can browse around the dir tree just fine, even opening /dev in
EWG> > what I  thought to be remarkable speed, but when I try to expand
EWG> > /home/gardnerj  it crashes everytime. I hope this hasn't been
EWG> > covered before, but this is the first time I've seen this behavior.
EWG> > Any ideas what might be causing this?
EWG> 
EWG> Please run xffm with gdb, and when it crashes obtain a backtrace with
EWG> "bt" at the gdb> prompt. That will pinpoint the cause. It's probably
EWG> some unexpected filename encountered.

Well this is what I got:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 8192 (LWP 19120)]
0x42073fe0 in _int_free () from /lib/i686/libc.so.6
(gdb) bt
#0  0x42073fe0 in _int_free () from /lib/i686/libc.so.6
#1  0x42074a2c in free () from /lib/i686/libc.so.6
#2  0x403d1ea4 in g_free () from /usr/lib/libglib-2.0.so.0
#3  0x0806f03f in resolve_icon (treeview=0x8155930, en=0x83bada9)
    at icons.c:403
#4  0x0806f3f9 in set_icon (treeview=0x8155930, iterator=0xbffff100)
    at icons.c:477
#5  0x0806d290 in add_file_info (treeview=0x8155930, iterator=0xbffff100, 
    en=0x83982a0, name=0x8398290 "-n") at add_file.c:199
#6  0x0806d3fd in add_it (treeview=0x8155930, target=0x8357d58,
en=0x83982a0,     name=0x8398290 "-n", insert=0) at add_file.c:218
#7  0x0806d473 in add_file (treeview=0x8155930, target=0x8357d58, 
    en=0x83982a0, name=0x8398290 "-n") at add_file.c:226
#8  0x0805cd83 in add_node_contents (treeview=0x8155930, iter=0x8357d58, 
    gdir=0xbffff1e8) at add_node_contents.c:173
#9  0x0805ca12 in add_folder (treeview=0x8155930, iter=0x8357d58)
    at add_folder.c:158
#10 0x08060c92 in open_dir (treeview=0x8155930, iter=0x8357d58, 
    treepath=0x80ab7f8, user_data=0x8155930) at callbacks.c:155
#11 0x401044f7 in _gtk_marshal_VOID__BOXED_BOXED ()
   from /usr/lib/libgtk-x11-2.0.so.0
#12 0x403720c0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#13 0x403868b4 in signal_emit_unlocked_R () from
/usr/lib/libgobject-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#14 0x40385888 in g_signal_emit_valist () from/usr/lib/libgobject-2.0.so.0
#15 0x40385af4 in g_signal_emit () from/usr/lib/libgobject-2.0.so.0
#16 0x401d2fbf in gtk_tree_view_real_expand_row ()   from
/usr/lib/libgtk-x11-2.0.so.0
#17 0x401c5e4a in gtk_tree_view_button_release ()   from
/usr/lib/libgtk-x11-2.0.so.0
#18 0x401030e4 in _gtk_marshal_BOOLEAN__BOXED
()   from /usr/lib/libgtk-x11-2.0.so.0
#19 0x40372467 in g_type_class_meta_marshal ()
   from /usr/lib/libgobject-2.0.so.0
#20 0x403720c0 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#21 0x40386369 in signal_emit_unlocked_R () from
/usr/lib/libgobject-2.0.so.0
#22 0x40385689 in g_signal_emit_valist () from
/usr/lib/libgobject-2.0.so.0
#23 0x40145fdf in gtk_signal_emit () from
/usr/lib/libgtk-x11-2.0.so.0
#24 0x401e9413 in gtk_widget_event_internal ()
   from /usr/lib/libgtk-x11-2.0.so.0
#25 0x40102e67 in gtk_propagate_event () from /usr/lib/libgtk-x11-2.0.so.0
#26 0x40101b45 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0
#27 0x402b3f21 in gdk_event_dispatch () from /usr/lib/libgdk-x11-2.0.so.0
#28 0x403cbf65 in g_main_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0x403ccf98 in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#30 0x403cd2ad in g_main_context_iterate () from
/usr/lib/libglib-2.0.so.0
#31 0x403cda1f in g_main_loop_run () from
/usr/lib/libglib-2.0.so.0
---Type <return> to continue, or q <return> to quit---
#32 0x4010139f in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#33 0x0806c456 in main (argc=1, argv=0xbffffdb4) at main.c:46
#34 0x420158d4 in __libc_start_main () from /lib/i686/libc.so.6
(gdb) 

Hope this helps, because I don't understand it very much at all, but I'm
just a user, with a learning disability when it comes to coding of any
sort.

Jonathan
-- 
There are only 10 kinds of people in this world:
Those who understand binary and those who don't.