Mac Crash

[lonadar]

I've been using a development version of 4.2.0 for a while after the rubble-trap crash ticked me off enough to compile a copy, and it's run very well (so much so I didn't realize 4.2.1 had been released) until just now. I'm posting this in case this isn't something that was fixed in 4.2.1 since I have no idea what happened, so I wouldn't know how to replicate it. Going to go get 4.2.1 now. :-)

Process:               angband [51935]
Path:                  /Applications/Angband.app/Contents/MacOS/angband
Identifier:            angband
Version:               4.2.0-dirty (???)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           angband [51935]
Date/Time:             2020-07-28 22:00:14.861 -0400
OS Version:            Mac OS X 10.13.6 (17G14019)
Report Version:        12

Time Awake Since Boot: 1000000 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000078
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [0]

VM Regions Near 0x78:
--> 
    __TEXT                 00000001090cd000-00000001091d2000 [ 1044K] r-x/rwx SM=COW  ## [/Applications/Angband.app/Contents/MacOS/angband]

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   org.rephial.angband           	0x000000010916b0f7 hit_trap + 583
1   org.rephial.angband           	0x000000010912168a monster_swap + 522
2   org.rephial.angband           	0x00000001090d8b7d move_player + 621
3   org.rephial.angband           	0x00000001090d8eae do_cmd_walk + 318
4   org.rephial.angband           	0x00000001090d9f41 process_command + 369
5   org.rephial.angband           	0x00000001090da0ef cmdq_pop + 111
6   org.rephial.angband           	0x00000001090e9af9 process_player + 377
7   org.rephial.angband           	0x00000001090e9e8e run_game_loop + 46
8   org.rephial.angband           	0x0000000109175e32 play_game + 258
9   org.rephial.angband           	0x00000001091a9988 +[AngbandContext beginGame] + 1560
10  org.rephial.angband           	0x00000001091acbf2 -[AngbandAppDelegate applicationDidFinishLaunching:] + 34
11  com.apple.CoreFoundation      	0x00007fff5689939c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
12  com.apple.CoreFoundation      	0x00007fff5689926a _CFXRegistrationPost + 458
13  com.apple.CoreFoundation      	0x00007fff56898fa1 ___CFXNotificationPost_block_invoke + 225
14  com.apple.CoreFoundation      	0x00007fff56857b32 -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1826
15  com.apple.CoreFoundation      	0x00007fff56856bc3 _CFXNotificationPost + 659
16  com.apple.Foundation          	0x00007fff58985047 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
17  com.apple.AppKit              	0x00007fff53f43206 -[NSApplication _postDidFinishNotification] + 313
18  com.apple.AppKit              	0x00007fff53f42e4f -[NSApplication _sendFinishLaunchingNotification] + 220
19  com.apple.AppKit              	0x00007fff53e15a7b -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 562
20  com.apple.AppKit              	0x00007fff53e156b1 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 690
21  com.apple.Foundation          	0x00007fff589c7ef4 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 287
22  com.apple.Foundation          	0x00007fff589c7d72 _NSAppleEventManagerGenericHandler + 102
23  com.apple.AE                  	0x00007fff5799ff08 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 1788
24  com.apple.AE                  	0x00007fff5799f7af dispatchEventAndSendReply(AEDesc const*, AEDesc*) + 41
25  com.apple.AE                  	0x00007fff5799f69d aeProcessAppleEvent + 383
26  com.apple.HIToolbox           	0x00007fff55b734a0 AEProcessAppleEvent + 55
27  com.apple.AppKit              	0x00007fff53e10cfa _DPSNextEvent + 2788
28  com.apple.AppKit              	0x00007fff545a6e34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
29  com.apple.AppKit              	0x00007fff53e0584d -[NSApplication run] + 764
30  com.apple.AppKit              	0x00007fff53dd4a3a NSApplicationMain + 804
31  org.rephial.angband           	0x00000001091acf99 main + 9
32  libdyld.dylib                 	0x00007fff7e8a2015 start + 1

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000600000a57df8  rcx: 0x00006000002a0248  rdx: 0x00006000000bf148
  rdi: 0x00007f94da016208  rsi: 0x0000000000000038  rbp: 0x00007ffee6b31300  rsp: 0x00007ffee6b312a0
   r8: 0x0000000000000023   r9: 0x0000000000000009  r10: 0x00006000001bdea8  r11: 0x00007f94daa86588
  r12: 0x00000001091c7828  r13: 0x0000000000000000  r14: 0x000060400026fb48  r15: 0x00000001091e4d58
  rip: 0x000000010916b0f7  rfl: 0x0000000000010206  cr2: 0x0000000000000078
  
Logical CPU:     0
Error Code:      0x00000004
Trap Number:     14


Binary Images:
       0x1090cd000 -        0x1091d1ff3 +org.rephial.angband (4.2.0-dirty - ???) <C20664F2-2839-3CA4-8885-8C50C3895837> /Applications/Angband.app/Contents/MacOS/angband

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 14
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 1042207
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=425.9M resident=0K(0%) swapped_out_or_unallocated=425.9M(100%)
Writable regions: Total=171.9M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=171.9M(100%)
 
Model: iMac10,1, BootROM 215.0.0.0.0, 2 processors, Intel Core 2 Duo, 3.06 GHz, 12 GB, SMC 1.53f13
Graphics: ATI Radeon HD 4670, ATI Radeon HD 4670, PCIe
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464B44
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E4D3136464D52
Memory Module: BANK 0/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
Memory Module: BANK 1/DIMM1, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020
Bluetooth: Version 6.0.7f22, 3 services, 27 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HDE721010SLA330, 1 TB
Serial ATA Device: PIONEER DVD-RW  DVRTS09
USB Device: USB 2.0 Bus
USB Device: Internal Memory Card Reader
USB Device: easystore 25FC
USB Device: USB 2.0 Bus
USB Device: Built-in iSight
USB Device: USB Bus
USB Device: IR Receiver
USB Device: USB Bus
USB Device: USB Trackball
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus:

[backwardsEric]

That looks like the result of the bug with ancient mechanism traps (this post is one of the other reports). That bug was fixed in the post 4.2.0 nightly versions from November 4th, 2019, and on and in 4.2.1.

[lonadar]

Just an FYI - the build I was using was after that was reported to have been fixed. (And, in fact, I confirmed the bug affecting me HAD been fixed because a savefile was able to successfully move through a point that had previously caused a repeatable crash.) That's why I shared this - if it is the same bug, then the build I was using didn't fix it completely (though, to be fair, it may have been later fixed "better").

[lonadar]

Appears I did have a save file, and after compiling from the source as of 8/29, I was able to clear the level. The only thing I saw that was different was a trap that blocked off the corridor with solid stone. The previous crash I was aware of was a trap that caused varied rubble to appear around you and stunned you. I hadn't seen this solid block trap before, so perhaps this trap was fixed after the rubble trap (and thus the build I had previously). If that's the trap you were referring to, I apologize, I wasn't aware of it.

[Nick]

Appears I did have a save file, and after compiling from the source as of 8/29, I was able to clear the level. The only thing I saw that was different was a trap that blocked off the corridor with solid stone. The previous crash I was aware of was a trap that caused varied rubble to appear around you and stunned you. I hadn't seen this solid block trap before, so perhaps this trap was fixed after the rubble trap (and thus the build I had previously). If that's the trap you were referring to, I apologize, I wasn't aware of it.

Yep, that was it