Closed GoogleCodeExporter closed 9 years ago
As promised in issue 236, I've been able to reproduce the bug and obtain
detailed
info (with -debug and -trace).
Logs:
- http://narc.ro/dwarves/run.no-read.log
- http://narc.ro/dwarves/run.all-ok.log
Sequence of steps:
1. ran DT, let it fail to detect running copy and just sit there.
2. ran DF, generated a new world (aborted the world generation after a short
time and
told to use it as it is), then embarked using "Play Now!". Paused as soon as
possible.
3. Asked DT to connect to the running game (timestamp 22:54:34.311 according to
log).
DT notified me of having lost connection.
4. Saved the fort in DF, then reloaded it.
5. Asked DT to connect again, but it completely failed to do anything. At this
point,
I exited DT and created run.no-read.log
6. Re-running DT, it successfully connected to the running game, and read the 7
dwarves. I toggled a skill on one of them, just for reassurance that it was
working,
then exited DT and created run.all-ok.log.
Speculation:
In both cases, DT says it was reading the creature vector from 0x02578774, but
in the
non-working case it only found one non-dwarf creature at that address, with
racial ID
0x0.
It may also be relevant that the memory segment summary is different (bearing
in mind
it's exactly the same instance of DF, which has been paused and thus hopefully
been
doing nothing between the two executions):
- non-working: 2010-mai.-21 22:54:34.395 TRACE MEMORY SEGMENT SUMMARY: accepted 502
rejected 188 total 690 [src\dfinstancewindows.cpp:386]
- working: 2010-mai.-21 22:55:47.229 TRACE MEMORY SEGMENT SUMMARY: accepted 514
rejected 199 total 713 [src\dfinstancewindows.cpp:386]
Original comment by octavs...@gmail.com
on 21 May 2010 at 8:21
another case of a bad creature vector. Fixed in r13ed26a2f010
Original comment by treyst...@gmail.com
on 31 May 2010 at 8:18
Original issue reported on code.google.com by
jhad...@gmail.com
on 20 May 2010 at 12:19Attachments: