One worry I am having with my patch now is, what happens if the first
element is the one being modified? Then itPrev is a null pointer. I
*think* from looking at the GLib code that g_list_next will then return
null when it it handed itPrev, which means "it" will be set to null,
which I believe will trigger the end of the loop. Assuming I know what
I'm looking at, that could put Openbox in an unusual state that could
cause problems later down the road.

To get around that, I can add a check to see if itPrev is null, and if
so, it will set "it" to stacking_list, which is where it is supposed to
end up.

(I'm trying to *not* use the patch from Arch Linux's forums, since I
really hate the fact that it has to loop through a bunch of the list
every time it modifies an element. That seems quite inefficient.)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2011751

Title:
  openbox crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2011751/+subscriptions


-- 
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

Reply via email to