From: Hans Ronne <hronne@comhem.se>
To: bd1@sysmatrix.net
Cc: xconq7@sources.redhat.com
Subject: Re: Newest code crashes Tcl/Tk
Date: Thu, 24 Jun 2004 03:36:00 -0000 [thread overview]
Message-ID: <l03130302bcffc84284ae@[212.181.162.155]> (raw)
In-Reply-To: <1ceee3937bc15cce62421882ce135cca@localhost>
>> Since you are using the CVS sources, perhaps you could make a couple of
>> checkouts with different dates, to verify that this change is responsible?
>> If that is the case, a checkout with -D 2004-06-20 should work while -D
>> 2004-06-21 should freeze (note that the dates in the ChangeLog do not
>> always agree with the checkout dates).
>
>Going backwards, the 6/12 (not 6/21) build seems to work fine, and
>anything after can lock up the machine while clicking on the world map to
>zoom to new locations. This includes after the game is quit but you may
>continue to look around.
Thanks! Is that the -D 2004-06-12 checkout, that is the one that contains
entries from 6/11 but not 6/12? In that case, I am surprised. Most of the
code that was checked in on 6/12 were fixes to the Mac interface or to the
Windows app, neither of which could explain your problem.
What remains are two things. One is Eric's fix to change_unit_type, which
is unlikely to be the cause of the freezes. The other is the following
changes relating to acp-independent units:
Fix update_unit_display buzzing for acp-independent units
that were waiting for a build task.
* plan.c (set_waiting_for_tasks): Return without calling
update_unit_display if the flag already is set.
Fix so that acp-independent building may resume in the same
turn if we change the build task and thus may have enough
material to build on the new unit type.
* task.c (set_build_task): Call set_unit_buildingdone to reset
the buildingdone flag to FALSE.
(push_build_task): Call set_unit_buildingdone to reset the
buildingdone flag to FALSE.
(resume_build_task): Call set_unit_buildingdone to reset the
buildingdone flag to FALSE.
Does the game where you see freezes have any acp-independent units?
Hans
next prev parent reply other threads:[~2004-06-24 0:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 6:50 GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
2004-06-21 8:11 ` Newest code crashes Tcl/Tk Brian Dunn
2004-06-21 16:22 ` Eric McDonald
2004-06-21 20:13 ` Hans Ronne
2004-06-24 0:04 ` Brian Dunn
2004-06-24 3:36 ` Hans Ronne [this message]
2004-06-24 4:21 ` Brian Dunn
2004-06-24 4:50 ` Eric McDonald
2004-06-24 6:28 ` Brian Dunn
2004-06-24 18:34 ` Eric McDonald
2004-06-24 7:15 ` Hans Ronne
2004-06-24 9:28 ` Brian Dunn
2004-06-24 9:41 ` Tcl/Tk update Brian Dunn
2004-06-24 17:08 ` Hans Ronne
2004-06-24 15:01 ` Tck/Tk info Brian Dunn
2004-06-27 6:16 ` Brian Dunn
2004-06-27 9:19 ` Hans Ronne
2004-06-24 16:59 ` Newest code crashes Tcl/Tk Jim Kingdon
2004-06-24 17:03 ` Hans Ronne
2004-06-24 17:30 ` Eric McDonald
2004-06-24 18:24 ` Hans Ronne
2004-06-21 16:25 ` GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
2004-06-22 3:25 ` Eric McDonald
2004-06-22 6:19 ` Jim Kingdon
2004-06-22 9:50 ` Juergen Ruehle
2004-06-22 14:18 ` RFC: Increment and Decrement (was Re: GDL Notice: Arithmetic Operators / Quasi-Formulae) Eric McDonald
2004-06-22 14:50 ` Jim Kingdon
2004-06-23 6:02 ` Eric McDonald
2004-06-23 6:17 ` Jim Kingdon
2004-06-23 13:40 ` RFC: Increment and Decrement (was Re: GDL Notice: ArithmeticOperators " Erik Jessen
2004-06-23 23:33 ` Autotesting (was Re: RFC: Increment and Decrement) Eric McDonald
2004-06-24 7:01 ` Jim Kingdon
2004-06-25 3:35 ` Eric McDonald
2004-06-22 14:03 ` GDL Notice: Arithmetic Operators / Quasi-Formulae Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='l03130302bcffc84284ae@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=bd1@sysmatrix.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).