[TIMOB-5853] iOS: Debugger: 10.6.8 only: Running the basic breakpoint in debugger cause simulator to eventually exit on it on
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Cannot Reproduce |
| Resolution Date | 2011-10-25T09:24:43.000+0000 |
| Affected Version/s | Release 1.7.4 |
| Fix Version/s | Sprint 2011-43 |
| Components | iOS |
| Labels | basic, debugger, exit, regression |
| Reporter | Natalie Huynh |
| Assignee | Stephen Tramer |
| Created | 2011-10-24T11:35:51.000+0000 |
| Updated | 2014-06-19T12:42:56.000+0000 |
Description
Steps to Reproduce:
1. Run Test case 1013 from http://wiki.appcelerator.org/display/tp/Debugger+Test+Plan
2. Go through all the steps from top to bottom
Actual Result:
By step 21-22 the simulator exits on its own
Expected Result:
Should not exit
Exit info:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
[DEBUG] Session did end with error Error Domain=DTiPhoneSimulatorErrorDomain Code=1 UserInfo=0x103001600 "The simulated application quit."
[INFO] Application has exited from Simulator
Note:
Last working with 1.7.4.v20111020142213 and 1.7.3
Occurs on Snow Leopard only. Lion works fine
Saw Natalie reproduce the error, but have been unable to reproduce it on a system which uses "official" toolchain elements (SDK 1.7.4.9e633fb, OS 10.6.8, Studio 1.0.6.201110202348, XCode 4.2.4C199 / iOS 5.0 SDK). Apparently the bug was reported against XCode 4.1, and persisted when the SDK was still selected as 4.3, but disappeared when it was swapped to 5.0. Probably means that a toolchain we don't support (XCode 4.1/SDK 4.3) was being invoked. Going to confirm this before marking the bug invalid/can't reproduce.
Unable to reproduce with the official toolchain set (as per previous comment). If it can be reproduced on a machine with a clean xcode 4.2 install (and no other xcode installs) then this bug should be reopened.
Uninstalled all the xcode off my machine and installed 4.2 only and not encountering the issue anymore