RE: breakpoints ignored while running unit tests! Why?
RE: breakpoints ignored while running unit tests! Why?
- Subject: RE: breakpoints ignored while running unit tests! Why?
- From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>
- Date: Wed, 10 Sep 2008 08:24:36 -0400
- Thread-topic: breakpoints ignored while running unit tests! Why?
Chris, like Pat, I wanted to say thank you for helping us out. Below is
both the settings I used, and the step-by-step actions of what I did.
Is this sufficient for you to figure out what is going on?
Thanks,
Cem Karan
XCode Unit Test Debugging
- Settings - I'm only listing what is customized
- Project Settings
- Build Tab - I only build in debug, so that is what I'm listing
- Architectures - Standard (32-bit Universal)
- Base SDK - Mac OS X 10.5
- Build Active Architecture Only - YES
- Prebinding - NO
- Optimization Level - None [-O0]
- C Language Dialect - C99 [-std=c99]
- Other C Flags - -DOSX_UNIT_TESTS
- Targets
- Unit tester - The test bundle
- General Tab
- Direct Dependencies - FOCU_S tester - The application
I'm testing
- Build Tab
- Bundle Loader
-
$(BUILT_PRODUCTS_DIR)/$(PROJECT_NAME).app/Contents/MacOS/$(PROJECT_NAME)
- Evaluates to "build/Debug/FOCU_S
tester.app/Contents/MacOS/FOCU_S tester"
- Test Host
-
$(BUILT_PRODUCTS_DIR)/$(PROJECT_NAME).app/Contents/MacOS/$(PROJECT_NAME)
- Evaluates to "build/Debug/FOCU_S
tester.app/Contents/MacOS/FOCU_S tester"
- Executable
- FOCU_S tester
- General Tab
- The working directory is set to the Build Products
directory
- Arguments tab - all checkboxes are checked
- Arguments
- -SenTest All
- Environment
- DYLD_INSERT_LIBRARIES
-
$(DEVELOPER_LIBRARY_DIR)/PrivateFrameworks/DevToolsBundleInjection.frame
work/DevToolsBundleInjection
- DYLD_FALLBACK_FRAMEWORK_PATH
- $(DEVELOPER_LIBRARY_DIR)/Frameworks
- XCInjectBundle
- $(BUILT_PRODUCTS_DIR)/Unit Tester.octest
- XCInjectBundleInto
- $(BUILT_PRODUCTS_DIR)/FOCU_S
tester.app/Contents/MacOS/FOCU_S tester
- My actions
- Notes
- 1 I tried a number of different actions to see if one of them
would work.
- 2 Since I want to know what is happening in the unit tests, my
breakpoints are in the unit tests only.
- 3 The code I am debugging is exercised via the unit tests
alone; my application currently doesn't instantiate any of
the classes I'm debugging.
- 4 Unit test code is part of the Unit Tester target's sources.
Application code is part of the FOCU_S tester target.
- 5 Like Pat, my breakpoints turn orange once I start debugging.
I don't know what this means, or why this occurs.
- 6 When debugging, I get no warnings or errors in the GDB
console
window; the generic window (I haven't put together a GUI yet)
comes up, and (I'm guessing) the run loop is waiting for
input,
but since nothing comes, it just kind of sits there.
- First attempt
- 1 Clean the FOCU_S tester target via Clean All
- 2 Clean the Unit tester target via Clean All
- 3 Build the FOCU_S tester target
- 4 Build the Unit tester target
- This fails as expected.
- 5 Bring up the debugging window (via the menu Run->Debugger)
- 6 Debug the FOCU_S tester target
- Generic window comes up, but my breakpoint is skipped
- Second attempt
- 1 Clean the FOCU_S tester target via Clean All
- 2 Clean the Unit tester target via Clean All
- 3 Build the FOCU_S tester target
- 4 Build the Unit tester target
- This fails as expected.
- 5 Place a breakpoint on a succeeding test
- 6 Bring up the debugging window (via the menu Run->Debugger)
- 7 Debug the Unit tester target
- Generic window comes up, but my breakpoint is skipped
- Third attempt
- 1 Clean the FOCU_S tester target via Clean All
- 2 Clean the Unit tester target via Clean All
- 3 Comment out the failing test.
- 4 Build the FOCU_S tester target
- 5 Build the Unit tester target
- This succeeds as expected.
- 6 Bring up the debugging window (via the menu Run->Debugger)
- 7 Debug the FOCU_S tester target
- Generic window comes up, but my breakpoint is skipped
- Fourth attempt
- 1 Clean the FOCU_S tester target via Clean All
- 2 Clean the Unit tester target via Clean All
- 3 Comment out the failing test.
- 4 Build the FOCU_S tester target
- 5 Build the Unit tester target
- This succeeds as expected.
- 6 Place a breakpoint on a succeeding test
- 7 Bring up the debugging window (via the menu Run->Debugger)
- 8 Debug the Unit tester target
- Generic window comes up, but my breakpoint is skipped
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >breakpoints ignored while running unit tests! Why? (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>) |
| | >Re: breakpoints ignored while running unit tests! Why? (From: Philippe Casgrain <email@hidden>) |
| | >RE: breakpoints ignored while running unit tests! Why? (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>) |
| | >Re: breakpoints ignored while running unit tests! Why? (From: Chris Hanson <email@hidden>) |
| | >RE: breakpoints ignored while running unit tests! Why? (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>) |
| | >Re: breakpoints ignored while running unit tests! Why? (From: Chris Hanson <email@hidden>) |
| | >RE: breakpoints ignored while running unit tests! Why? (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>) |
| | >Re: breakpoints ignored while running unit tests! Why? (From: Chris Hanson <email@hidden>) |
| | >RE: breakpoints ignored while running unit tests! Why? (From: "Karan, Cem (Civ, ARL/CISD)" <email@hidden>) |
| | >Re: breakpoints ignored while running unit tests! Why? (From: Chris Hanson <email@hidden>) |