aboutsummaryrefslogtreecommitdiffhomepage
path: root/content/2021-05-15-pthread_cancel-noexcept.md
diff options
context:
space:
mode:
Diffstat (limited to 'content/2021-05-15-pthread_cancel-noexcept.md')
-rw-r--r--content/2021-05-15-pthread_cancel-noexcept.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/2021-05-15-pthread_cancel-noexcept.md b/content/2021-05-15-pthread_cancel-noexcept.md
index 4ff0fc2..f09cadc 100644
--- a/content/2021-05-15-pthread_cancel-noexcept.md
+++ b/content/2021-05-15-pthread_cancel-noexcept.md
@@ -8,7 +8,7 @@ tags = ["linux", "threading", "c++"]
Few weeks ago I was debugging a random crash in a legacy code base at work. In
case the crash occurred the following message was printed on `stdout` of the
process:
-```text
+```
terminate called without an active exception
```
@@ -21,7 +21,7 @@ exception, the initial assumption was one of the following:
After receiving a backtrace captured by a customer it wasn't directly obvious
to me why `std::terminate()` was called here. The backtrace received looked
something like the following:
-```text
+```
#0 0x00007fb21df22ef5 in raise () from /usr/lib/libc.so.6
#1 0x00007fb21df0c862 in abort () from /usr/lib/libc.so.6
#2 0x00007fb21e2a886a in __gnu_cxx::__verbose_terminate_handler () at /build/gcc/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95