UIKit should use a custom logging function that forwards to NSLog, so one can add breakpoints to it.
| Originator: | steipete | ||
| Number: | rdar://23455889 | Date Originated: | 08-Nov-2015 04:17 PM |
| Status: | Open | Resolved: | |
| Product: | iOS SDK | Product Version: | 9.1 |
| Classification: | Enhancement | Reproducible: | Always |
Summary: Some frameworks like CoreGraphics use a custom log function like CGPostError for logging API issues. This is very useful, as one can set a breakpoint to it. UIKit, on the other hand, simply uses NSLog. Since NSLog is used everywhere, it’s very hard to set a breakpoint and not be interrupted all the time. I’m not aware of a way a breakpoint could be set that only logs if it’s within UIKit. A much simpler and better way would be to use a function like UIKitLogError that forwards to NSLog. There’s basically no performance penalty and this can be done without breaking backwards compatibility. This would make debugging a lot easier.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!