All projects: Extracting diagnostics from recent versions.
∞labs products used to provide extended diagnostic information in certain builds (such as "nightlies") and very small amounts of diagnostic information in release (end-user) builds. In the future, release builds will have the option of providing you extended diagnostic information, similarly to diagnostic-enabled builds in the past. By default, such diagnostic information will however be turned off.
Current support.
This article will be updated as applications become compatible with the diagnostics scheme.
The following applications are compatible with the new diagnostics scheme:
- Mover 1.0.1 or later
The following applications and libraries are expected to become compatible in future updates:
- PlugSuit
- Afloat
- Unified Build Tools
- MuiKit
- RAM Assistant from BuyDifferent.
Turning on diagnostics in Mac programs by ∞labs.
To turn diagnostics on in Mac programs, you must use a command to add a new key to the defaults of the specific program. You will also need the identifier of the Labs program you want to turn diagnostics on for.
No Mac programs by ∞labs currently support extended diagnostics.
For example, to turn diagnostic in a program whose identifier is net.infinite-labs.SomeProgram, open Terminal and write the following command:
defaults write net.infinite-labs.SomeProgram L0ShowOnRequestLogging -bool YES
You will find extended diagnostics in the Console application (under Applications > Utilities > Console).
To disable diagnostics, repeat the above commands with NO rather than YES.
Turning on diagnostics for PlugSuit and ∞labs extenders like Afloat
To turn diagnostics on for PlugSuit and ∞labs extenders, you must turn them on for the applications they load in.
Current release versions of PlugSuit and Afloat do not support extended diagnostics.
For example, to gather diagnostics on PlugSuit and Afloat loaded in the TextEdit application, you need to turn diagnostics on using TextEdit's identifier, as per Mac applications above:
defaults write com.apple.TextEdit L0ShowOnRequestLogging -bool YES
You can also turn on diagnostics for all applications on your Mac as follows:
defaults write NSGlobalDomain L0ShowOnRequestLogging -bool YES
To disable diagnostics, repeat the above command with NO rather than YES.
Turning on diagnostics for iPhone applications by ∞labs
To turn diagnostics on for iPhone applications, use the Settings application on your iPhone.
To enable gathering diagnostics, do the following:
Press the Home button to return to your Home screen, then touch the Settings icon to open that application.
Scroll to the bottom of the list to reveal the entry corresponding to your application and touch it. For example, if you want to enable diagnostics for Mover, scroll the list to the Mover entry and touch it.
Touch the Advanced entry at the bottom of the list.
Turn on the Diagnostics switch.
You will find extended diagnostics in the iPhone's console. To display the console, use the iPhone Configuration Utility application on your Mac or Windows computer while the iPhone is connected to it. You can download the appropriate version from the Apple iPhone Enterprise support site.
To disable diagnostics, turn off the appropriate Diagnostics switch again in Settings.
Turning on diagnostics for command-line applications by ∞labs.
Command-line applications can have diagnostics turned on using an environment variable set before running them.
No ∞labs command line applications support this at the moment. Support for this in the ∞labs unified build tools is expected in the future.
To enable logging, you must set the ILABS_L0ShowOnRequestLogging environment variable to a value of YES. For example, to run the tool utility with diagnostics enabled in a Bourne shell such as bash, run it as follows:
export ILABS_L0ShowOnRequestLogging=YES
./tool --option
Diagnostics output will be written to the standard error.
To disable diagnostics for subsequent runs, unset the ILABS_L0ShowOnRequestLogging variable or set its value to something other than YES (for example, NO).
