This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/20020] GDB segfault on printing objects
- From: "snyder at bnl dot gov" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Thu, 18 Jan 2018 03:25:03 +0000
- Subject: [Bug c++/20020] GDB segfault on printing objects
- Auto-submitted: auto-generated
- References: <bug-20020-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20020
scott snyder <snyder at bnl dot gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |snyder at bnl dot gov
--- Comment #8 from scott snyder <snyder at bnl dot gov> ---
I've started seeing this when printing C++ std::atomic<T*> values.
Here's the reproducer i came up with:
-- x.cc -----------------------------
template<typename _Tp>
struct foo
{
static constexpr bool is_always_lock_free = true;
};
int main()
{
foo<int> p;
return 0;
}
---------------------------------------------------------
Then with
gcc version 7.2.1 20170915 (Red Hat 7.2.1-2) (GCC)
we get
$ /usr/bin/gcc -g -o x x.cc -std=c++17
$ ~/tmp/gdb/gdb-8.0.1/gdb/gdb ./x
...
GNU gdb (GDB) 8.0.1
...
Reading symbols from ./x...done.
(gdb) break main
Breakpoint 1 at 0x40048b: file x.cc, line 11.
(gdb) run
Starting program: /home/sss/atlas/dvtest/x
Breakpoint 1, Python Exception <type 'exceptions.NameError'> Installation
error: gdb.execute_unwinders function is missing:
main () at x.cc:11
11 return 0;
(gdb) p p
$1 = {
Segmentation fault (core dumped)
The crash is the same as reported earlier in this thread.
--
You are receiving this mail because:
You are on the CC list for the bug.