boost/stacktrace
2
0
Fork 0
mirror of https://github.com/boostorg/stacktrace.git synced 2026-01-28 07:42:11 +00:00
Code Issues Projects Releases Wiki Activity

Remove doubtful example from 'Getting Started' section

Browse Source
This commit is contained in:
Antony Polukhin
2017-07-04 23:31:23 +03:00
parent 77e69f036b
commit ba2f260d95
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
doc/stacktrace.qbk
View File

@@ -65,7 +65,7 @@ Segmentation Faults and `std::terminate` calls sometimes happen in programs. Pro
`std::terminate` calls `std::abort`, so we need to capture stack traces on Segmentation Faults and Abort signals.
[warning Writing a signal handler requires high attention! Only a few system calls allowed in signal handlers, so there's no cross platform way to print a stacktrace without a risk of deadlocking. The only way to deal with the problem - [*dump raw stacktrace into file/socket/shared memory and parse it on program restart].]
[warning Writing a signal handler requires high attention! Only a few system calls allowed in signal handlers, so there's no cross platform way to print a stacktrace without a risk of deadlocking. The only way to deal with the problem - [*dump raw stacktrace into file/socket and parse it on program restart].]
Let's write a handler to safely dump stacktrace:
@@ -240,7 +240,7 @@ Terminate called:
[endsect]
[/
[section Store stacktraces into shared memory]
There's a way to serialize stacktrace in async safe manner and share that serialized representation with another process. Here's another example with signal handlers.
@@ -275,7 +275,8 @@ Previous run crashed and left trace in shared memory:
15# 0x0000000000402999
```
[endsect]
[endsect]
]
[endsect]