Nightly chardump bug

[fph]

Started playing an old character with r7dda-blah (the April 9 nightly); when I take a chardump, the file is written only partially and then the game crashes. Apparently, the crash happens when the game tries to write the weight of my main weapon (which is also the first object weight that gets written to the savefile). The crash does not happen if I create a new character and save its chardump.

I am playing the Windows nightly using Wine 1.2.2 on Ubuntu 10.04.2 (too lazy to compile ). I attach the savefile for easier debugging.

The reason why I wanted to take a chardump is that I have just found a randart phial that can be activated for mass genocide. WTF?
(btw, currently at 107HP; if I had first activated it in the wrong place, probably it could have killed me...)

[Magnate]

Started playing an old character with r7dda-blah (the April 9 nightly); when I take a chardump, the file is written only partially and then the game crashes. Apparently, the crash happens when the game tries to write the weight of my main weapon (which is also the first object weight that gets written to the savefile). The crash does not happen if I create a new character and save its chardump.

I am playing the Windows nightly using Wine 1.2.2 on Ubuntu 10.04.2 (too lazy to compile ). I attach the savefile for easier debugging.

The reason why I wanted to take a chardump is that I have just found a randart phial that can be activated for mass genocide. WTF?

That indicates that something is corrupted, as the Phial cannot get that activation. So that's probably why the dump is crashing for that savefile.

If anybody else gets a crash from a chardump, please post here.

[fph]

That indicates that something is corrupted, as the Phial cannot get that activation. So that's probably why the dump is crashing for that savefile.

Ok, I imagined something like that. Was savefile compatibility changed recently? This character was created with a nightly not too far ago (post-3.2 IIRC). Otherwise I should start worrying about my hard disk...

[Magnate]

Don't worry, myshkin worked it out with some splendid savefile-fu.

The maul your character is carrying was dropped by a monster which has subsequently been deleted from monster.txt (Soldier - there was a consolidation of similar monsters a while back). So the "origin_xtra" field (which monster dropped it) contains a now-illegal value, which causes the crash (it doesn't point to a name that can be printed).

We can fix this for the future by checking explicitly for this in describe_origin, and actually printing "dropped by a monster which no longer exists, at 2500 feet"!