开发者

NSXMLParser throwing EXC_BAD_ACCESS

开发者 https://www.devze.com 2023-02-08 21:20 出处:网络
It is normal to have such issues but I am currently stuck in knowing how it works. Whenever I use NSXMLparser to parse the URL and store in the database, it gets parsed for the first time but when I p

It is normal to have such issues but I am currently stuck in knowing how it works. Whenever I use NSXMLparser to parse the URL and store in the database, it gets parsed for the first time but when I parse it again it throws EXC_BAD_ACCESS. Here is my code:

- (void) initParse {

    [super init];

    appleAppDelegate = (appleAppDelegate*开发者_如何学Python)[[UIApplication sharedApplication] delegate];

    NSURL *url = [[[NSURL alloc] initWithString:@"http:example.com/file.xml"] autorelease];

    self.parser1 = [[[NSXMLParser alloc] initWithContentsOfURL:url] autorelease] ;

    [parser1 setShouldResolveExternalEntities:NO];
    [parser1 setDelegate:self];

    [parser1 parse];

}

When it reaches the end of the function at "}", it throws EXC_BAD_ACCESS. I am not sure what is wrong since I am releasing my URL and even my parser. Has any one come across this situation.

Sagos


Try running with NSZombieEnabled - that will tell you the type of the object which is being accessed after being freed.


You are accessing a released object which is exactly your problem, make sure you release at the end and make sure everything you need is still around.

0

精彩评论

暂无评论...
验证码 换一张
取 消