Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates
 209.85.214.175 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CABiQX1XyU+g=5nUz=+nh-Wiy+j-URnX8mv0kTQVp-chH-pKJPA@mail.gmail.com>
References: 
 <CADjNb+mkdC5fuo+ghkcBMKTWLhCg+R1XHZBFsRySNVjUosBHAw@mail.gmail.com>
 <CABiQX1XyU+g=5nUz=+nh-Wiy+j-URnX8mv0kTQVp-chH-pKJPA@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Wed, 5 Sep 2012 14:53:32 -0400
Message-ID: 
 <CABiQX1U4LTSOMhRbEO+HLeoWHAeGg_sC+z_=r98mwJgo458WJQ@mail.gmail.com>
Subject: Re: Getting Crash in Mobile-spec file tests on iOS 2.1.0rc2
To: Andrew Grieve <agrieve@chromium.org>
Cc: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8f839adb63758004c8f8e520

--e89a8f839adb63758004c8f8e520
Content-Type: text/plain; charset=ISO-8859-1

In the case I was hitting, it was a pretty obvious forgetting to nil check
error. Fix commit:
https://git-wip-us.apache.org/repos/asf?p=incubator-cordova-ios.git;a=commit;h=e1781b0302ff51cb65581f08b783a420f6371ede

I think in this case it would pass on the simulator but BAD_ACCESS
on-device.

I'm not seeing a failure in File related tests though. Tried going back &
forth a few times on both iPhone 3gs and iPad2.


On Wed, Sep 5, 2012 at 2:38 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> Just tried this on my 3gs and got a BAD_ACCESS within FileTransfer upload
> on my first try. Looking into it...
>
>
> On Wed, Sep 5, 2012 at 12:20 PM, Becky Gibson <gibson.becky@gmail.com>wrote:
>
>> I am getting an inconsistent crash when I run the automated mobile-spec
>> file tests on the iOS simulator or my iPhone 4S.  Sometimes the tests run
>> fine but others I get an EXEC_BAD_ACCESS.  Can someone else please test?
>>  You may need to run the test multiple times (just go back out of a
>> successful file test and try again - at most it only takes me 3 tries to
>> crash).
>>
>> I tried setting breakpoints on execptions,  I also tried profiling with
>> zombies but neither provided any useful info. It seems related to the file
>> move tests - either with  *entry.move.fnp.file1 or *entry.move.dsp.srcDir
>> as the src.  And of course, if I step through the code for those move test
>> sin the debugger it doesn't crash.
>>
>> I'll try creating  a new project to see if that helps.
>>
>> -becky
>>
>
>

--e89a8f839adb63758004c8f8e520--