https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112541
Bug ID: 112541
Summary: FAIL: 19_diagnostics/stacktrace/current.cc
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: testsuite-fail
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
Target: armv8l-unknown-linux-gnueabihf
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/snapshots/gcc.git~master/libstdc++-v3/testsuite/19_diagnostics/stacktrace/current.cc:52:
test_max_depth()::<lambda()>::<lambda()>::<lambda()>::<lambda()>::<lambda()>::<lambda()>::<lambda()>::<lambda()>:
Assertion '! t.empty()' failed.
timeout: the monitored command dumped core
FAIL: 19_diagnostics/stacktrace/current.cc -std=gnu++23 execution test
Also:
terminate called after throwing an instance of 'std::out_of_range'
what(): basic_stack_trace::at: bad frame number
timeout: the monitored command dumped core
FAIL: 19_diagnostics/stacktrace/entry.cc -std=gnu++23 execution test
It appears that __stacktrace_impl::_S_current returns an empty sequence of
frames.
It's possible that all the lambda frames are inlined, or skip+2 in
stacktrace.cc causes us to skip real frames that we should keep, or maybe
libbacktrace just doesn't work on this target.
