<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - SIGSEGV on desktop-shell focus change" href="https://bugs.freedesktop.org/show_bug.cgi?id=100878#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - SIGSEGV on desktop-shell focus change" href="https://bugs.freedesktop.org/show_bug.cgi?id=100878">bug 100878</a> from <a class="email" href="mailto:worknesday@gmail.com" title="worknesday@gmail.com">worknesday@gmail.com</a> <pre>(In reply to Daniel Stone from <a href="show_bug.cgi?id=100878#c2">comment #2</a>) > The clue, however, is in the names of the parameters to the functions. For > instance, you do: > struct wl_list list; > struct { > int something; > struct wl_list link; > } foo; > > wl_list_init(&list); > wl_list_insert(&list, &foo->link); > wl_list_remove(&foo->link); > > At this point, foo has been removed from list (making its link member > dangling), but the overall list itself is still valid. Trying to remove a > list from itself does not make any real sense; instead, you remove an > element from that list. ah, I see! So, does that mean the list itself is represented as an always-present dummy-node that resides in the list? However, it looks like the crash occurred as a result of es->destroy_signal.listener_list.prev being NULL. Somehow, this list ceased to be circular (at least while traversing backwards)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>