EmuNewz Network
OS X: Access violation reading location 0x0 at 0x0. - Printable Version

+- EmuNewz Network (https://www.emunewz.net/forum)
+-- Forum: Official Boards for Emunews Affiliated Emu Projects (https://www.emunewz.net/forum/forumdisplay.php?fid=47)
+--- Forum: Official RPCS3 Forum [archive] (https://www.emunewz.net/forum/forumdisplay.php?fid=172)
+---- Forum: RPCS3 - Support & Issue Reporting (https://www.emunewz.net/forum/forumdisplay.php?fid=163)
+---- Thread: OS X: Access violation reading location 0x0 at 0x0. (/showthread.php?tid=174592)

OS X: Access violation reading location 0x0 at 0x0. - l2dy - 06-24-2016

I compiled it myself on OS X 10.11.5 with llvm and wxWidgets from Homebrew (didn't clone these two submodules and used -DLLVM_DIR=/usr/local/opt/llvm). No errors during compilation but when I boot a game "Access violation reading location 0x0 at 0x0." shows up in the terminal. Log file was huge (42M raw, 3.4M compressed) so I'm posting the last few line in post and the first few in attachment.
Code:
vm::g_base_addr = 0x10a282000
vm::g_priv_addr = 0x20a282000
Fatal error:
Access violation reading location 0x0 at 0x0.
HOW TO REPORT ERRORS:
1) Check the FAQ, readme, other sources. Please ensure that your hardware and software configuration is compliant.
2) You must provide FULL information: how to reproduce the error (your actions), RPCS3.log file, other *.log files whenever requested.
3) Please ensure that your software (game) is 'Playable' or close. Please note that 'Non-playable' games will be ignored.
4) If the software (game) is not 'Playable', please ensure that this error is unexpected, i.e. it didn't happen before or similar.
Please, don't send incorrect reports. Thanks for understanding.
Abort trap: 6

Code:
$ tail -n 25 RPCS3.log
·! LDR: Extended: 0x1d8970 (0x218 --> 0x258)
·! LDR: Extended: 0x1d8970 (0x258 --> 0x330)
·! LDR: Extended: 0x1d8af0 (0x98 --> 0xd8)
·! LDR: Extended: 0x1d8af0 (0xd8 --> 0x1b0)
·! LDR: Extended: 0x1d8b88 (0x40 --> 0x118)
·! LDR: Extended: 0x1d8de8 (0x450 --> 0x918)
·! LDR: Extended: 0x1d8de8 (0x918 --> 0x980)
·! LDR: Extended: 0x1d9238 (0x4c8 --> 0x530)
·! {PPU[0x1] Thread (main_thread) [0x001e3028]} sysPrxForUser: sys_initialize_tls(thread_id=0x1, addr=*0x200008, size=0x0, mem_size=0x780)
·S LDR: (S)ELF: boot done.
·! {PPU[0x1] Thread (main_thread) [0x001e3028]} sysPrxForUser: TLS initialized (addr=0x21c000, size=0x7b0, max=0x42)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x1030b4a8, attr=*0x102e3fe0)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x1030b478, attr=*0x102e3fe0)
·W {PPU[0x1] Thread (main_thread) [0x001d7b08]} sys_memory: sys_memory_allocate(size=0x400000, flags=0x400, alloc_addr=*0xd00ff7a0)
·W {PPU[0x1] Thread (main_thread) [0x001d9a18]} cellGcmSys: _cellGcmInitBody(context=**0xd00ffa20, cmdSize=0x10000, ioSize=0x200000, ioAddress=0x20100000)
·W {PPU[0x1] Thread (main_thread) [0x001d9a18]} cellGcmSys: *** local memory(addr=0xc0000000, size=0xf900000)
·W {PPU[0x1] Thread (main_thread) [0x001d9a18]} cellGcmSys: cellGcmInit(): 256MB io address space used
·W {PPU[0x1] Thread (main_thread) [0x001d9d90]} cellSysutil: cellVideoOutConfigure(videoOut=0, config=*0xd00ffab0, option=*0x0, waitForEvent=0)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x1030b420, attr=*0x102e3fe0)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x21c630, attr=*0x102e3820)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x21c6f0, attr=*0x102e3820)
·W {PPU[0x1] Thread (main_thread) [0x001da440]} sysPrxForUser: sys_lwmutex_create(lwmutex=*0x21c7b0, attr=*0x102e3820)
·! {rsx::thread} RSX: 2.1 INTEL-10.14.66
·! {rsx::thread} RSX: 1.20
·! {rsx::thread} RSX: Intel Inc.


RE: OS X: Access violation reading location 0x0 at 0x0. - Annie - 06-26-2016

Probably worth giving a shot reporting over at github. I don't think RPCS3 has been tested on OS X for a while, might be part of one of 0.0.0.9's regressions.