This patch takes a different approach. It removes GTK locking and forces all GTK operations into the main thread via g_idle_add. This approach has the advantage that it doesn't require knowing whether the main thread or some worker thread is attempting to performing the operations. It also has the advantage that it will probably fix other crash bugs specific to Windows, since the Windows GTK backend does not support multithreaded access to the windowing system.
Anyone see any obvious problems with this approach? ** Patch added: "remove GTK locking, use g_idle instead" http://launchpadlibrarian.net/53257891/use-g-idle.patch -- Once selected interface, if "Hosts List" is open and click on "Scan for hosts" Ettercap crash https://bugs.launchpad.net/bugs/588007 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
