>>>>> "d" == dan <[EMAIL PROTECTED]> writes:
d> What are you doing in such situation?
Glare at source (^^;)
1) If it crushes in case like when you tip a "search",
then it must be miss-handling of Launch code.
2) If it crushes only while you are playing, next thing you should
do is check the size of stack you are using, and size of stack
avaliable. This is important especially when you are using
recursive call, but not only that case.
3) try to keep the log. Try your best to keep the log of what
player have done, and what computer have done.
and see if it can be repeated using Gremlin on POSE.
4) use gdb's -command(or -x) option and try to keep the
log of step by step actions. With Gremlin, you can make
perfect single step log of your code.
Don't forget to take the stack queue and register image.
If you are lucky enough, you'll get the information you need.
# But this is the very last resort, for it takes lots of time
# ... like ... about week or so? ..., and diskspace ... even if you
# used gzip with you ...., and if you fail, you'll get nothing from
# it.
5) If even this "last resort" did not work, then.
What I usually do, is throw away the source code,
take some rest for about 1 week, and re-build the code from
scratch.
# What else can you do....
----
Kenichi Okuyama@ Tokyo Research Lab. IBM-Japan. Co.
