Follow-up Comment #14, bug #21272 (project freeciv):

> Here is a 3rd version of this bug.

> And yes the top of the call stack is again 
> gdk_win32_drawable_get_handle. 
...and again, common suffix starts at gdk_window_new() and what's below that
is different.

Here's the decode for the bit of Freeciv code in the middle:

0FB01DC  C:\MyGames\Freeciv\libgtk-win32-2.0-0.dll:00FB01DC  gtk_widget_show
00FBE2F1  C:\MyGames\Freeciv\libgtk-win32-2.0-0.dll:00FBE2F1 
00430383  _popup_unit_select_dialog
00424AD6  _do_map_click
0042E993  _butt_down_mapcanvas
00E9733A  C:\MyGames\Freeciv\libgtk-win32-2.0-0.dll:00E9733A 
63A43B7A  C:\MyGames\Freeciv\libgobject-2.0-0.dll:63A43B7A  g_closure_invoke

(Since this is the unit select dialog, this might have been clicking on a
team-mate's city?)

I'm reasonably willing to believe that this is a random Gtk failure with a
chance of occurring whenever a window is popped up.

> A question: if this is an old gtk bug why did it not happen
> before, for instance in LT30 which also used freeciv version 2.3 
Good question. From Google, I think LT30 ran from about Jan-Aug 2012, right?
The latest clients available in that period were 2.3.1 and 2.3.2; the Windows
builds might well have been using an even older version of Gtk which didn't
have the bug (but I haven't checked).

> I guess it doesn't matter if it goes away with the new version 
> of gtk 
We've got no evidence that it will yet, it's just a guess. On the other hand,
I have no better ideas.


Reply to this item at:


  Message sent via/by Gna!

Freeciv-dev mailing list

Reply via email to