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 8198947
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T06:04:16+00:00 2026-06-07T06:04:16+00:00

I have a weird problem. I am declaring an NSError : NSError *error; Right

  • 0

I have a weird problem.

I am declaring an NSError :

 NSError *error;

Right after that I am checking for the error and I get the “self” class.

 NSLog(@"Error: %@", error);

And the result :

2012-07-07 20:48:55.489 JerusalemBiblicalZoo[54204:1e407] Error:
ParseHelper

Any Ideas ?

Tanks

Shani

  • 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-07T06:04:18+00:00Added an answer on June 7, 2026 at 6:04 am

    Saying NSError *error; just declares a pointer to an error object. Unless you initialize it (such as with NSError *error = nil), it will be a random garbage value. (Which, in this case, is self.)

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

Sidebar

Related Questions

I have a weird problem. I develop my sites on localhost and after that
I have a weird problem where after setting nocheck on a foreign constraint and
I have a weird problem that i can't figure out a solution for: I've
I have a weird problem: I extended Zend_Log with a class called \Application\Log (it
I have a weird problem building a release of an erlang application that I'm
I have a weird problem. I have a script that loads images into the
I have a weird problem that only started recently. When I run the app
I have a weird problem with Magento cache. I have an extension that have
I have a WEIRD problem with Future.get() in Java. It returns always with an
I have a weird problem , below are two simple get calls and returning

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.