Jump to content

Mac OS 11 Big Sur

By sitjs

· 7222 views
  • Undefined
  • Ticket solved.
  • FMRTE 20
  • Build: 0
  • Game Store: Steam
  • Game Version: 20.1.4-1318685

 

Process:               FmrteAvalonia [6821]
Path:                  /Applications/FMRTE 20.app/Contents/MacOS/FmrteAvalonia
Identifier:            com.braca.iFMRTE20
Version:               1.0 (19.3.0)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           FmrteAvalonia [6821]
User ID:               501

Date/Time:             2020-08-27 20:11:39.757 +0200
OS Version:            Mac OS X 10.16 (20A5354i)
Report Version:        12
Bridge OS Version:     5.0 (18P50358b)
Anonymous UUID:        DE0F25EE-0E25-C7BF-9CBF-2A5D0CC9DFE3

Sleep/Wake UUID:       1105443A-F4D9-4B43-9180-7DFC10FE77EE

Time Awake Since Boot: 58000 seconds
Time Since Wake:       800 seconds

System Integrity Protection: disabled

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

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    LIBSYSTEM, [0x2]

Application Specific Information:
dyld: in dlsym()
assertion failure: "(self)->_enumeratingSubviewsCount < ((1 << 6) - 1)" -> %lld

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib            0x00007fff6c1577e2 __abort_with_payload + 10
1   libsystem_kernel.dylib            0x00007fff6c159229 abort_with_payload_wrapper_internal + 80
2   libsystem_kernel.dylib            0x00007fff6c15925b abort_with_payload + 9
3   libsystem_c.dylib                 0x00007fff6c0ae73b _os_crash_fmt.cold.1 + 55

Thunderbolt Bus: MacBook Air, Apple Inc., 47.4
 

error.log 0 B
  • Report

    • User Feedback

    Recommended Comments

    Newbie

    Sandro Gattuso

    Members
    comment_791
    1 hour ago, BraCa said:

    Can you please run this in terminal, and post the results

      

    
csrutil status

     

    Hi Braca, 

    here the output. Seems that instead of disabling the Debugging restrictions the command (csrutil enable --without debug) disabled the FS protection, not sure why?

    I've also tried to run a `csrutil clear`, reboot, then again `csrutil enable --without debug`, reboot and checked again the status, still some outcome.

    Am I doing something wrong or it could be a Big Sur bug?  

    240587263_ScreenShot2020-11-19at8_43_16am.thumb.png.c37858ceaa88e4539cd751855fe570b1.png

  • Quote
    • Rookie

    jenny francis

    Members
    comment_793
    39 minutes ago, Sandro Gattuso said:

    Hi Braca, 

    here the output. Seems that instead of disabling the Debugging restrictions the command (csrutil enable --without debug) disabled the FS protection, not sure why?

    I've also tried to run a `csrutil clear`, reboot, then again `csrutil enable --without debug`, reboot and checked again the status, still some outcome.

    Am I doing something wrong or it could be a Big Sur bug?  

    240587263_ScreenShot2020-11-19at8_43_16am.thumb.png.c37858ceaa88e4539cd751855fe570b1.png

    I am having this same issue. I think you have to use something called opencore but I cant find anywhere to download a working version. 

  • Quote
    • Rookie

    thodinson

    Members
    comment_795

    Hi everyone

     

    Looks like without debug is not working in big sur. Got it working with the following  

    csrutil disable --with kext --with dtrace --with nvram --with basesystem
  • Quote
    • Newbie

    Sandro Gattuso

    Members
    comment_800
    9 hours ago, thodinson said:

    Hi everyone

     

    Looks like without debug is not working in big sur. Got it working with the following  

    
csrutil disable --with kext --with dtrace --with nvram --with basesystem

    Nice one Thodinson, thanks :)

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    Important Information

    We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.