Comment 74 for bug 36581

Yesterday I looked briefly about at all list manipulation areas,
but didn't see anything glaring either. Doesn't see like random memory
access, however. The l->next pointers are valid, just creating a loop.
I think the directory was being changed while this happened (during
daily rawhide update). Is there any async event which could change
the tree? AFAICT, gam_tree_get_children() expects the parent node to
remain queiscent. You said it's not multithreaded, how about signal
driven? Any way for gam_tree_add() to happen during a
gam_tree_get_children so that the GNode sibling list changes while
building the GList?