Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8252035
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 8, 20262026-06-08T00:26:02+00:00 2026-06-08T00:26:02+00:00

I received a crash report from a user saying the application crashes when it

  • 0

I received a crash report from a user saying the application crashes when it starts.
I drag the crash report to Xcode 4 and received below information (this is an extract),
but Xcode 4 doesn’t symbolicate line 10, 24, 25 which I really want to see.

I use atos command:

atos -arch armv6 -o 'MyApp.app'/'MyApp' 0x0000449b

but all it shows is:
0x0000449b (in MyApp) + 64

Do you have any idea how can I read the symbols in line 10, 24, 25?

Incident Identifier: 5142E671-BD08-483A-AAF2-F7D680BE0267
CrashReporter Key:   481fe1c162975f8367127b52824e30d33ffaa014
Hardware Model:      iPhone4,1
Process:         MyApp [2463]
Path:            /var/mobile/Applications/79DE9C42-332C-4243-B637-9DCF6AC4EC35/MyApp.app/MyApp
Identifier:      MyApp
Version:         ??? (???)
Code Type:       ARM (Native)
Parent Process:  launchd [1]

Date/Time:       2012-07-04 11:37:39.362 -0600
OS Version:      iPhone OS 5.1.1 (9B206)
Report Version:  104

Exception Type:  EXC_CRASH (SIGABRT)
Exception Codes: 0x00000000, 0x00000000
Crashed Thread:  0

Last Exception Backtrace:
0   CoreFoundation                  0x353a188f __exceptionPreprocess + 163
1   libobjc.A.dylib                 0x37748259 objc_exception_throw + 33
2   CoreFoundation                  0x353a4a9b -[NSObject doesNotRecognizeSelector:] + 175
3   CoreFoundation                  0x353a3915 ___forwarding___ + 301
4   CoreFoundation                  0x352fe650 _CF_forwarding_prep_0 + 48
5   Foundation                      0x34eaf4ff __57-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_0 + 19
6   CoreFoundation                  0x3536d547 ___CFXNotificationPost_block_invoke_0 + 71
7   CoreFoundation                  0x352f9097 _CFXNotificationPost + 1407
8   Foundation                      0x34e233eb -[NSNotificationCenter postNotificationName:object:userInfo:] + 67
9   Foundation                      0x34e24c1b -[NSNotificationCenter postNotificationName:object:] + 31
10  MyApp                       0x0000449b 0x1000 + 13467
11  UIKit                           0x32e19c31 -[UIApplication _stopDeactivatingForReason:] + 189
12  UIKit                           0x32eb1381 -[UIApplication _handleApplicationResumeEvent:] + 1141
13  UIKit                           0x32dd5b03 -[UIApplication handleEvent:withNewEvent:] + 1075
14  UIKit                           0x32dd5567 -[UIApplication sendEvent:] + 55
15  UIKit                           0x32dd4f3b _UIApplicationHandleEvent + 5827
16  GraphicsServices                0x36f9422b PurpleEventCallback + 883
17  CoreFoundation                  0x35375523 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 39
18  CoreFoundation                  0x353754c5 __CFRunLoopDoSource1 + 141
19  CoreFoundation                  0x35374313 __CFRunLoopRun + 1371
20  CoreFoundation                  0x352f74a5 CFRunLoopRunSpecific + 301
21  CoreFoundation                  0x352f736d CFRunLoopRunInMode + 105
22  GraphicsServices                0x36f93439 GSEventRunModal + 137
23  UIKit                           0x32e03cd5 UIApplicationMain + 1081
24  MyApp                       0x00004b27 0x1000 + 15143
25  MyApp                       0x00003cd0 0x1000 + 11472
  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-08T00:26:04+00:00Added an answer on June 8, 2026 at 12:26 am

    I didn’t find the answer on how to read memory addresses in my crash log.

    But I have figured out how to fix the bug:
    – this crash shows that it’s caused by Local Notification
    – [NSObject doesNotRecognizeSelector:] is raised

    So I search for all Local Notifications in the project, and find the corresponding selector for each observer one of the selector is not implemented. That’s why I received
    -[NSObject doesNotRecognizeSelector:
    and the app crashed.

    Implement the missing selector fixed the problem.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I received the following crash report in my Android application when trying to call
A user has sent in a crash report with the stack trace listed below
I recieved a crash report from MadExcept from a user. The Exception was Invalid
Today I received a crash report because in the following snippet w and/or h
I received the following crash report (truncated) Exception Type: EXC_CRASH (SIGSEGV) Exception Codes: 0x00000000,
I have a published app and received a stack trace from a crash: android.view.WindowManager$BadTokenException:
I recently received a 64-bit crash dump from a customer. Our processes are all
I just published my first application to Google Marketplace and received the information, that
I received the first crash report but I am not able to get what
Our C# application calls MinidumpWriteDump upon an unhandled exception. I have received some crash

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.