You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: stacktrace.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ <h2>I. Motivation</h2>
58
58
7# 0x00007F991FD69F45 in /lib/x86_64-linux-gnu/libc.so.6
59
59
8# 0x0000000000401139
60
60
</pre>
61
-
<p>We propose two headers (<code><stacktrace></code> and <code><frame></code>), two classes (<code>template <typename Allocator>class basic_stacktrace</code> and <code>class frame</code>) and several functions for safe stack frames dump.</p>
61
+
<p>We propose one header (<code><stacktrace></code>), two classes (<code>template <typename Allocator>class basic_stacktrace</code> and <code>class frame</code>) and several functions for safe stack frames dump.</p>
62
62
63
63
<!--<p>Current compilers can print a stack trace while debugging or crash dump for debugging purposes. The compiler's users also can get a stack trace via implementation-defined API. But there is no cross-platform solution (except Boost.Stacktrace on which this Proposal is based of).</p>
64
64
<p>This is an attempt to solve the problem in a generic way on a library level and provide wording for thing being a standard de-facto on all compilers.</p>
0 commit comments