https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #18 from Jonathan Wakely ---
But we can remove the [8 Regression] marker if it's messing with reports.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #17 from Jonathan Wakely ---
Ideally I want the printer to still work for users with older versions of gdb.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #16 from Jakub Jelinek ---
So just add a gdb >= 8.1 version test in
libstdc++-v3/testsuite/lib/gdb-test.exp
and guard this test on effective target gdb_8_1?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|ASSIGNED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
H.J. Lu changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #13 from Pedro Alves ---
Fix is now in GDB's master, 8.1, and 8.0 branches.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #12 from Pedro Alves ---
GDB fix posted here:
https://sourceware.org/ml/gdb-patches/2018-01/msg00482.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #11 from Pedro Alves ---
Running the testcase under valgrind and current gdb master I see:
==6118== Conditional jump or move depends on uninitialised value(s)
==6118==at 0x4C35CB0: bcmp (vg_replace_st
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Pedro Alves changed:
What|Removed |Added
CC||palves at redhat dot com
--- Comment #10 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Jakub Jelinek changed:
What|Removed |Added
CC||palves at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #7 from Jakub Jelinek ---
Actually, the bug seems to FAIL at random, as shown by:
while :; do echo -n .; make check RUNTESTFLAGS=prettyprinters.exp=80276.cc >
/dev/null 2>/dev/null; grep -q ^FAIL testsuite/libstdc++.log && break; done
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #5 from H.J. Lu ---
(In reply to Jonathan Wakely from comment #4)
> Ah, or maybe the typedef std::__cxx11::string is not in the debug info, so
> the type printer doesn't know that std::__cxx11::basic_string is the
> same type as std::
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #4 from Jonathan Wakely ---
Ah, or maybe the typedef std::__cxx11::string is not in the debug info, so the
type printer doesn't know that std::__cxx11::basic_string is the same
type as std::__cxx11::string.
In testsuite/libstdc++-pre
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #2 from H.J. Lu ---
type =
std::unique_ptr, std::allocator >>[]>>[99]>^M
got: type =
std::unique_ptr, std::allocator >>[]>>[99]>^M
FAIL: libstdc++-prettyprinters/80276.cc whatis p4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
--- Comment #1 from Jonathan Wakely ---
What is shown in the libstdc++.log file before the FAIL line?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83906
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.0
19 matches
Mail list logo
