LinkedLog is a Xcode plugin that includes a Xcode PCH header file template that adds the macros `LLog` and `LLogF` and parses their output to link from the console to the corresponding file and line.
Title says it all - doesn't work.
How can you debug it?
Enable LinkedLog in Xcode 6.4, disable in 7ß3, build in 7ß3 and Run/Debug.
Launch Xcode 6.4, attach that in 7ß3, then debug a simple hello-world project with LLog statements in 6.4. LinkedLog in 6.4 will execute and parse the debugstring, and Xcode 7ß3 will break at breakpoints.
Right?
The plugin must provide the possibility to add the LLog definition to a project with a PCH file in place.
This could be a menu item in the edit menu to insert the definition at the cursor location or automatically to the existing PCH file
Additional: ConsoleTextView is not empty. When I debug my APP with breakpoint by Step over, Xcode do crash!
Application Specific Information:
ProductBuildVersion: 6C131e
UNCAUGHT EXCEPTION (NSRangeException): *** -[__NSCFString substringFromIndex:]: Index 240 out of bounds; string length 180
For me the regex doesn't match. Im running Xcode7.2 with the latest alcatraz build and I never see any blue, underlined, clickable text
regex seems to be "^[\d]{4}-[\d]{2}-[\d]{2}\s[\d]{2}:[\d]{2}:[\d]{2}.[\d]{3}\s[^\[][\d:\d_]\s(.+/([^\/:]+:\d+)):\s._"
sample line from the log (1st line) = "2016-02-15 16:22:16.330 myApp LIVE[26556:136834] /Users/dpich/Documents/MySources/myaapp-ios/myApp/Classes/AppDelegate.m:68: didFinishLaunch"
Hey @julian-weinert , the project is such a neat / thisshouldalreadyexistApple / useful idea!
I apologize if this is out of the scope of the project but I was wondering if it would be difficult to extend the linking to all log statements, say any obvious [File name]:[Line number] match.
Considering how many log libraries are out there that people are tied to, especially libraries that by now are very extensive, it would be awesome if LinkedLog was agnostic to logging method you used, just so long as you matched an obvious pattern.