Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Mobile and Embedded
  4. Bad Access in application:didFinishLaunchingWithOptions:

Bad Access in application:didFinishLaunchingWithOptions:

Scheduled Pinned Locked Moved Unsolved Mobile and Embedded
1 Posts 1 Posters 282 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • C Offline
    C Offline
    Colton
    wrote on last edited by
    #1

    I'm having trouble tracking down a bug. Every so often a customer on an iOS 15+ device experiences a crash which is reported through Sentry error tracking. I am using Qt 5 with a custom AppDelegate. The exception is:

    EXC_BAD_ACCESS: __cxa_guard_release > _setInvalidatesViewsOnAppearanceChange: > application:didFinishLaunchingWithOptions: >
    KERN_INVALID_ADDRESS at 0x10.
    

    When looking at the stacktrace, it never intersects with user-space code. How can I identify the line that caused it? What is __cxa_guard_release? Is it a known bug with Qt 5?
    Here is the stacktrace reported by Sentry:
    In QList<T>::Node::t > QObject::connect > std::__1::function<T>::operator() > QList<T>::swap > <redacted>

    1 Reply Last reply
    0

    • Login

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Get Qt Extensions
    • Unsolved