Provide line numbers on stack trace
| Originator: | jeff | ||
| Number: | rdar://16629974 | Date Originated: | 4/15/2014 |
| Status: | Open | Resolved: | No |
| Product: | Developer Tools | Product Version: | Xcode 5.1.1 |
| Classification: | Feature (New) | Reproducible: | Not Applicable |
.NET and JS provide references to the offending line number when a program crashes. Objective-C / LLDB on the other hand only gets as specific as a method name. This makes debugging much more difficult than it needs to be. It looks like there are cryptic ways <http://stackoverflow.com/a/18135512> of determining the offending line of compiled(?) code, but that's very convoluted and a pain in the ass. It would be a HUGE benefit to developers if LLDB could determine what line of uncompiled code is throwing fits.
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!