search

elimelec / inethack

Automatically exported from code.google.com/p/inethack
GNU General Public License v2.0
0 stars 0 forks source link

Enable INSURANCE #40

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
There were problems with INSURANCE so I had to leave it out, but with all
the crashes it's a prerequisite for even locating them.

Original issue reported on code.google.com by din...@gmail.com on 8 Aug 2009 at 7:57

GoogleCodeExporter commented 8 years ago 
Could you clarify what the problems were?

Original comment by ciawal@gmail.com on 8 Aug 2009 at 8:18

GoogleCodeExporter commented 8 years ago 
The lock file. Tries to create lock1 und then complains about lock0 not being
present, something like that ...

Original comment by din...@gmail.com on 9 Aug 2009 at 6:19

GoogleCodeExporter commented 8 years ago 
INSURANCE won't work, you need a utility (recover). Triggering an ordinary save 
might
be good ...

Original comment by din...@gmail.com on 9 Aug 2009 at 6:59

GoogleCodeExporter commented 8 years ago 
ordinary saves didn't work either (were discarded at restart)

Original comment by din...@gmail.com on 9 Aug 2009 at 11:29

GoogleCodeExporter commented 8 years ago

Original comment by din...@gmail.com on 11 Aug 2009 at 10:52

GoogleCodeExporter commented 8 years ago 
r125 attempts this

Original comment by ciawal@gmail.com on 13 Aug 2009 at 2:47

GoogleCodeExporter commented 8 years ago 
Just checked this out, after compiling and running through half a level I got a 
phone call. When I went back into 
iNetHack after the call it asked me if I wanted to use the recovery info!! I 
said yes, and it restarted me at the 
beginning of the level.

So, on one hand, good work! On the other, why did it not simply save the state 
for a normal resume when I 
elected to take the phone call? :)

Original comment by kevinh...@gmail.com on 13 Aug 2009 at 3:02

GoogleCodeExporter commented 8 years ago 
Did it do that previously? I wouldn’t have expected this to change any saving 
behaviour.

Original comment by ciawal@gmail.com on 13 Aug 2009 at 3:04

GoogleCodeExporter commented 8 years ago 
Well to be honest I'm not sure. I'd never received a call while in iNetHack. 
Funny coincidence, or maybe that was 
always broken?  I'll see if I can stage the same details and repeat it here.

Original comment by kevinh...@gmail.com on 13 Aug 2009 at 3:27

GoogleCodeExporter commented 8 years ago 
Ok, I tried calling myself from another line. This time I was able to answer 
the call, hang up, and then return into 
the game normally. 

Might have been because it was running with the debugger when I took the first 
call that caused a crash when I 
unplugged it. If so, then I'd call that a successful test ;)

Original comment by kevinh...@gmail.com on 13 Aug 2009 at 3:32

GoogleCodeExporter commented 8 years ago 
r125 was a significant change IMO and I postponed the beta because of it. Fixed 
some
problems in r126, some of which where present but were highlighted in r125 due 
to
panic messages (try quitting while in character selection ...)

Original comment by din...@gmail.com on 14 Aug 2009 at 8:52

GoogleCodeExporter commented 8 years ago 
Anyone seen any problems with this? Should we close it?

Original comment by ciawal@gmail.com on 16 Aug 2009 at 2:22

GoogleCodeExporter commented 8 years ago 
closed for now, please reopen should problems arise

Original comment by din...@gmail.com on 17 Aug 2009 at 10:20