4.0.1 Bugs

[Nivra]

Quick update on the OS X crashes.

The most common OS X crash I get nowadays has to do with the sub-windows.

I play on a 12" MacBook Air, so screen space is at a premium. Every so often, I move stuff around, and that results in a crash, usually just after I reposition a subwindow, and then click on the title bar of a subwindow.

[Nick]

Just entered a spiral lesser vault and used the Phial, but it only lights up its area, not all the corridors of the spiral. Didn't it used to light the whole vault?

It should still - that looks like a bug.

[Ingwe Ingweron]

Just entered a spiral lesser vault and used the Phial, but it only lights up its area, not all the corridors of the spiral. Didn't it used to light the whole vault?

[Nick]

Yeah, I know 4.0.2 is out, but I haven't moved to it, yet. Here's a segfault in 4.0.1, just in case it's a new one.

Recalled to 99. Sauron is already dead. Crash was immediate (i.e., no user input after recall):

Thanks, I'll have a look.

[Derakon]

At least in standard American English it's "are" because you're talking about all the iron shod boots. But if you weren't, and just that pair under discussion, then it's "is." Apologies for the pedantry: the paper grader in me get out.

Note that then you're talking about the pair of boots, i.e. "pair" is the noun, and it's a singular noun. You could have multiple pairs of boots that collectively are something, but a single pair of boots is something.

[StMicah]

hmm... "boots is" or "boots are". Single set of multiple items. I can't tell which is right.

At least in standard American English it's "are" because you're talking about all the iron shod boots. But if you weren't, and just that pair under discussion, then it's "is." Apologies for the pedantry: the paper grader in me get out.

[Timo Pietilä]

Another one that's not really a bug, but has never made sense to me...

Why are mithril items heavier than iron or steel?

For example, Iron Shod Boots weigh 3.5 lbs while Mithril Shod Boots weigh 4.0 lbs. Mithril is supposed to be incredibly light.

For most items Mithril is already lighter than their other metallic equals, but it seems that iron shod boots is lighter which makes it exception to the rule.

That's tiny change, I would just change Mithril to 25 instead of 40.

hmm... "boots is" or "boots are". Single set of multiple items. I can't tell which is right.

[Ingwe Ingweron]

Another one that's not really a bug, but has never made sense to me...

Why are mithril items heavier than iron or steel?

For example, Iron Shod Boots weigh 3.5 lbs while Mithril Shod Boots weigh 4.0 lbs. Mithril is supposed to be incredibly light.

"Mithril! All folk desired it. It could be beaten like copper, and polished like glass; and the Dwarves could make of it a metal, light and yet harder than tempered steel. Its beauty was like to that of common silver, but the beauty of mithril did not tarnish or grow dim."

[kandrc]

Yeah, I know 4.0.2 is out, but I haven't moved to it, yet. Here's a segfault in 4.0.1, just in case it's a new one.

Recalled to 99. Sauron is already dead. Crash was immediate (i.e., no user input after recall):

Program received signal SIGSEGV, Segmentation fault.
0x0000000000405051 in wiz_light (c=0xe4b678, full=false) at cave-map.c:451
451                                                     cave_k->squares[yy][xx].feat = c->squares[yy][xx].feat;
(gdb) print yy
$1 = 22
(gdb) print xx
$2 = 2
(gdb) print cave_k
$3 = (struct chunk *) 0xac2698
(gdb) print *cave_k
$4 = {name = 0x0, created_at = 444691, depth = 0, feeling = 0 '\000', 
  obj_rating = 0, mon_rating = 0, good_item = false, height = 22, width = 66, 
  feeling_squares = 0, feat_count = 0xb25848, feat = 0x0, m_idx = 0x0, 
  squares = 0xbe6a88, monsters = 0xce2b68, mon_max = 1, mon_cnt = 0, 
  mon_current = -1}
(gdb) print *c
$5 = {name = 0x0, created_at = 445451, depth = 99, feeling = 0 '\000', 
  obj_rating = 519228, mon_rating = 2434635, good_item = false, height = 33, 
  width = 61, feeling_squares = 0, feat_count = 0xb39528, feat = 0x0, 
  m_idx = 0x0, squares = 0xc39588, monsters = 0xa21fb8, mon_max = 34, 
  mon_cnt = 33, mon_current = -1}
(gdb) bt
#0  0x0000000000405051 in wiz_light (c=0xe4b678, full=false) at cave-map.c:451
#1  0x00000000004207ad in labyrinth_gen (p=0x83eaa8) at gen-cave.c:882
#2  0x000000000041e00f in cave_generate (c=0x738ee0 <cave>, p=0x83eaa8)
    at generate.c:878
#3  0x000000000041c148 in run_game_loop () at game-world.c:806
#4  0x00000000004a5943 in play_game (new_game=false) at ui-game.c:430
#5  0x00000000004dcc66 in main (argc=1, argv=0x7fffffffdc78) at main.c:552
(gdb)

[Ingwe Ingweron]

I sometimes wish running would stop if next to treasure vein. I mostly play dwarfs, and they are excellent at digging so wasting a turn to dig treasure out is not actually waste for them (also takes about 0.3 secs real time).

I believe it does now. This was fixed during the 4.0 beta.

[Timo Pietilä]

More a request than a bug... when the level feeling kicks in, could we have that be a disturb condition that stops @ running?

I sometimes wish running would stop if next to treasure vein. I mostly play dwarfs, and they are excellent at digging so wasting a turn to dig treasure out is not actually waste for them (also takes about 0.3 secs real time).

[Ingwe Ingweron]

More a request than a bug... when the level feeling kicks in, could we have that be a disturb condition that stops @ running?

[Nick]

Here's a repeatable crash: pickup or identify (on the ground) that white amulet.

It's on the most current nightlie (db7f828) and can't remember any crashes on ID'ing something. I'm pretty sure I ID'd another unknown amulet (maybe wisdom) on this version earlier.

Edit: curiosity got the better of me. I ran the previous version (from 8/24) and identification worked just fine: it's evenstar. Opened db7f828 and the amulet is ID'd and no crashing. I hope that helps in figuring out the crash.

Yeah - turns out I'd only introduces that bug in db7f828 (where it should crash the game on finding any artifact). There's a new build up now with the bug fixed.

[StMicah]

Here's a repeatable crash: pickup or identify (on the ground) that white amulet.

It's on the most current nightlie (db7f828) and can't remember any crashes on ID'ing something. I'm pretty sure I ID'd another unknown amulet (maybe wisdom) on this version earlier.

Edit: curiosity got the better of me. I ran the previous version (from 8/24) and identification worked just fine: it's evenstar. Opened db7f828 and the amulet is ID'd and no crashing. I hope that helps in figuring out the crash.

[Nick]

Not necessarily a "bug", in that this has always been this way, but...

Is there a reason that once a ?Deep Descent is read, Rest '&' does not work the way it does for say, ?Recall ? When read from town, it's a minor annoyance to have to always enter a turncount while waiting for the deep descent to kick in.

Done in development; also now prints "Descent" on the status line after reading and before the descent.