v39lfy / google-toolbox-for-mac

Automatically exported from code.google.com/p/google-toolbox-for-mac
Apache License 2.0
0 stars 0 forks source link

line 23: 82687 Abort trap when running RunIPhoneUnitTest.sh #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
* Following directions to add new run script to unit testing target.

What is the expected output? What do you see instead?
* I expected for test case to fail assertion but instead got the following
error:
Running custom shell script (1 error)
line 23: 82687 Abort trap "$TARGET_BUILD_DIR/$EXECUTABLE_PAT"
-RegisterForSystemEvents
* This also seems to cause the iPhone simulator to crash before it comes up
since I get a dialog window saying so.

What version of the product are you using? On what operating system?
Mac OS X 10.5.6 with XCode 3.1.2

Please provide any additional information below.
I saw that the comments for writing iPhone unit tests includes this same
problem from another person.

Original issue reported on code.google.com by chris.st...@gmail.com on 28 Apr 2009 at 6:38

GoogleCodeExporter commented 9 years ago
Did you have the simulator running at the time it happened?

Is there a crash log for the app?

Original comment by thoma...@gmail.com on 29 Apr 2009 at 12:17

GoogleCodeExporter commented 9 years ago
Same problem.  OSX 10.5.6, XCode 3.1.3.  iPhone Simulator _not_ running.

Original comment by adam.str...@gmail.com on 7 May 2009 at 9:55

Attachments:

GoogleCodeExporter commented 9 years ago
Adam - different problem.  You're using a pretty old copy of the library, 
please pull directly from subversion.  
The as the iPhone SDK has changed, we haven't spun a zip with every release, 
and just asked people to pull 
directly from svn.

Original comment by thoma...@gmail.com on 8 May 2009 at 1:07

GoogleCodeExporter commented 9 years ago
It looks like I had the iPhone simulator running which is in the directions. It 
would
be nice if the usage page would tell what error you get if the simulator is 
running
but it was there. I was getting build successful but a popup box would come up
afterwards.

Also, I found out that I had to set the UnitTests active target configuration 
"Build
SDK" in "Information" to iPhone simulator rather than Mac OS X.

Seems these took care of the issue. Thanks.

Original comment by chris.st...@gmail.com on 8 May 2009 at 1:16

GoogleCodeExporter commented 9 years ago
It looks like I had the iPhone simulator running which is in the directions. It 
would
be nice if the usage page would tell what error you get if the simulator is 
running
but it was there. I was getting build successful but a popup box would come up
afterwards.

Also, I found out that I had to set the UnitTests active target configuration 
"Build
SDK" in "Information" to iPhone simulator rather than Mac OS X.

Seems these took care of the issue. Thanks.

Original comment by chris.st...@gmail.com on 8 May 2009 at 1:17

GoogleCodeExporter commented 9 years ago
It looks like I had the iPhone simulator running which is in the directions. It 
would
be nice if the usage page would tell what error you get if the simulator is 
running
but it was there. I was getting build successful but a popup box would come up
afterwards.

Also, I found out that I had to set the UnitTests active target configuration 
"Build
SDK" in "Information" to iPhone simulator rather than Mac OS X.

Seems these took care of the issue. Thanks.

Original comment by chris.st...@gmail.com on 8 May 2009 at 1:17

GoogleCodeExporter commented 9 years ago
It looks like I had the iPhone simulator running which is in the directions. It 
would
be nice if the usage page would tell what error you get if the simulator is 
running
but it was there. I was getting build successful but a popup box would come up
afterwards.

Also, I found out that I had to set the UnitTests active target configuration 
"Build
SDK" in "Information" to iPhone simulator rather than Mac OS X.

Seems these took care of the issue. Thanks.

Original comment by chris.st...@gmail.com on 8 May 2009 at 1:17

GoogleCodeExporter commented 9 years ago
Chris, the Notes section has one of the errors, what error you get has changed 
over time, I'll add this one also.  
If you started with a Cocoa Touch target, it should have set the SDK for you, 
it sounds like you might have 
changed the SDK along the way?

Original comment by thoma...@gmail.com on 8 May 2009 at 1:51

GoogleCodeExporter commented 9 years ago
Thomas-
You're right, for that dump I had imported the wrong (old) version of the 
toolkit.  However, I'm still getting the 
Bus Error from when using the SVN trunk (crash dump attached).  Looks like it's 
running the tests, tho...

a

Original comment by adam.str...@gmail.com on 8 May 2009 at 3:07

Attachments:

GoogleCodeExporter commented 9 years ago
On closer inspection, it would appear to be a different error...  I'll create a 
new issue for tracking.

a

Original comment by adam.str...@gmail.com on 8 May 2009 at 3:09