On Tue, 15 Jul 2008 11:36:46 -0700, Markus Spoettl
[EMAIL PROTECTED] said:
Hi List,
I've a problem I am failing to track down (let alone understand)
for a couple of weeks now. My application imports XML files that
contain - amongst other things - dates. Once in a while, the string to
date
Hi List,
I've a problem I am failing to track down (let alone understand)
for a couple of weeks now. My application imports XML files that
contain - amongst other things - dates. Once in a while, the string to
date conversion causes a crash (EXC_BAD_ACCESS):
#0 0x90b1da14 in
I didn't see any code sniglet for this, but it's not something simple
like:
[[NSDate alloc] initWithString:...];
vs
[[NSDate alloc] initWithString:@...];
i.e.: passing CString vs NSString?
On Jul 15, 2008, at 4:12 PM, Kyle Sluder wrote:
On Tue, Jul 15, 2008 at 2:36 PM,
On Jul 15, 2008, at 12:36 PM, Markus Spoettl wrote:
Any ideas what could be causing something like this?
In addition to what everyone else has suggested, have you tried
running your application under Guard Malloc to make sure memory is not
being corrupted? I've caught all sorts of weird
On Jul 15, 2008, at 5:00 PM, Nick Zitzmann wrote:
In addition to what everyone else has suggested, have you tried
running your application under Guard Malloc to make sure memory is
not being corrupted? I've caught all sorts of weird behavior in
applications before by using Guard Malloc.
On Jul 15, 2008, at 7:28 PM, Markus Spoettl wrote:
Thanks for the suggestion, I just tried this and now it crashes in
initialization of NSXMLDocument (see call stack below). My
(unfounded) suspicion was that the XMLDocument somehow was
responsible for all the trouble.
Have you reported
On Jul 15, 2008, at 6:33 PM, Nick Zitzmann wrote:
Have you reported this to Apple through http://bugreport.apple.com/
? That is very strange behavior that obviously shouldn't be
happening.
I will do this once I can confirm my crashes are gone. Obviously this
takes a little extra effort
