<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Bumping because I'd hate to see this get buried. It's a big pain point right now not getting any information from a fatalError, assert, or precondition other than the message.<br></div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Is there anything technical preventing this?</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Also some kind of name demangling would probably be necessary for this as well.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">- Harlan</div><div id="AppleMailSignature"><br></div><div>On Dec 7, 2015, at 4:47 PM, Harlan Haskins via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=us-ascii">Is there even a way to display the call stack symbols in pure Swift without <font face="Menlo" class="">NSThread.callStackSymbols()</font>?<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 7, 2015, at 4:24 PM, Radoslaw Pietruszewski via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">+ 1. This should also be generalized to assert, precondition, etc. If there was a way for custom fatalError-like functions to also dump a stack trace, that would be great.<br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></div></blockquote></div><br class=""></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=z0Ft8gvIaLt1zLwfkl4og6osLD9N8tlWJY1PY2zqWLWGP2gof-2BQMo8Oekd0-2BbSjmrkDYGPtrjJyMq-2BOVVCfhHn7DMVhHBYASohgdknbwuEZ1TSbFFOK5q25SHOWa8Omq8TQ9THLc3ixGKGKh2z5Od2J13ELZFHGqi-2Fp0-2BVCEFIQnNf-2F-2BkF-2Fv-2BMn4KRPYQq02DYZlAVdSz-2FysGa0puZUWcmrR8DlSKdxIyjh9aj0yqS0-3D" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;">
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>swift-evolution mailing list</span><br><span><a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a></span><br><span><a href="https://lists.swift.org/mailman/listinfo/swift-evolution">https://lists.swift.org/mailman/listinfo/swift-evolution</a></span><br></div></blockquote></body></html>