Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-10 Thread Michael Ash
On Fri, Apr 10, 2009 at 3:54 AM, david paeme wrote: > > On 10 Apr 2009, at 02:21, Greg Guerin wrote: > >> david paeme wrote: >> >>> instead of a string (%@) the >> >> >> %@ is the code for the -description of an object.  Strictly speaking, that >> isn't merely a string, but the result of sending a

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-10 Thread david paeme
On 10 Apr 2009, at 02:21, Greg Guerin wrote: david paeme wrote: instead of a string (%@) the %@ is the code for the -description of an object. Strictly speaking, that isn't merely a string, but the result of sending a message. UInt lastupdate = [userDefaults integerForKey:@"lastDB

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-09 Thread Greg Guerin
david paeme wrote: instead of a string (%@) the %@ is the code for the -description of an object. Strictly speaking, that isn't merely a string, but the result of sending a message. UInt lastupdate = [userDefaults integerForKey:@"lastDBUpdate"]; NSString *urlString = [NSString stringWi

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-09 Thread david paeme
I guess I solved the problem: I started thinking about why a locale would ever be needed - and all i could think of were strings and formatting. So I started fooling around with those... and the problem went away by using the userDefault differently: using a number (and %d) instead of a str

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-09 Thread Greg Guerin
david paeme wrote: This might be more interesting... looks like the thing some crash down in the bowels of LocaleGetValue? Locale information is often taken from environment variables. Print the environment, compare it to when it doesn't crash, and check any differences. Next, try runni

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-09 Thread david paeme
This might be more interesting... looks like the thing some crash down in the bowels of LocaleGetValue? As you probably gather, I have absolutely no idea what's going on in there... i've changed the code that launches this into the asymmetric request version for httpurlconnection (= threade

Re: NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-08 Thread Greg Parker
On Apr 8, 2009, at 5:55 AM, David Paeme wrote: I'm writing an application that accesses a http server via NSURLConnection's sendSynchronousRequest method, and it keeps crashing on me with an EXC_BAD_ADDRESS signal, without ever reaching the server. This is the stack trace: #0 0x9

NSURLConnection crashes with EXC_BAD_ADDRESS -- can't find why...

2009-04-08 Thread David Paeme
Hi all, I'm writing an application that accesses a http server via NSURLConnection's sendSynchronousRequest method, and it keeps crashing on me with an EXC_BAD_ADDRESS signal, without ever reaching the server. Here's sample code (very similar to what's in aaron hillegass' book):