http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45403
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45403
--- Comment #13 from Jonathan Wakely 2010-10-08
12:04:21 UTC ---
Author: redi
Date: Fri Oct 8 12:04:14 2010
New Revision: 165164
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=165164
Log:
PR libstdc++/45403
* python/libstdcxx/v6/
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45403
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |4.6.0
--- Comment #12 from Jonathan Wak
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45403
--- Comment #11 from Jonathan Wakely 2010-10-08
11:32:00 UTC ---
Author: redi
Date: Fri Oct 8 11:31:56 2010
New Revision: 165163
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=165163
Log:
PR libstdc++/45403
* python/libstdcxx/v6/
--- Comment #10 from pluto at agmk dot net 2010-09-16 14:04 ---
(In reply to comment #9)
> Are you sure you haven't modified your GCC sources?
i'm testing gcc-4.5 from svn branch, with gdb-7.2 and binutils-2.20.51.0.11.
filled as PR45690.
--
http://gcc.gnu.org/bugzilla/show_bug.cg
--- Comment #9 from redi at gcc dot gnu dot org 2010-09-15 23:52 ---
oops, I wasn't paying attention - I screwed up my build of gdb-7.2 so it didn't
have python support and mistook the non-pretty printed string for a traceback!
Here is a fresh GCC 4.5.2 build and a vanilla GDB 7.2 build
--- Comment #8 from redi at gcc dot gnu dot org 2010-09-15 23:43 ---
Hmm, OK, I can reproduce that with a current 4.5.2 build, but not with a
snapshot from last week. Please file a separate bug for that, component=c++ -
thanks!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45403
--- Comment #7 from pluto at agmk dot net 2010-09-15 11:34 ---
(In reply to comment #6)
> (In reply to comment #5)
> > with -gdwarf-4 enabled it fails on gdb-7.2 with runtime error:
>
> I couldn't reproduce that with 4.5.2 20100909, can you give more details?
$ cat t.cpp
#include
int
--- Comment #6 from redi at gcc dot gnu dot org 2010-09-15 11:21 ---
(In reply to comment #5)
> with -gdwarf-4 enabled it fails on gdb-7.2 with runtime error:
I couldn't reproduce that with 4.5.2 20100909, can you give more details?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45
--- Comment #5 from pluto at agmk dot net 2010-09-15 07:52 ---
there's one more issue with std::string pretty printing.
with -gdwarf-4 enabled it fails on gdb-7.2 with runtime error:
$1 = Traceback (most recent call last):
File
"/local/devel/toolchain45/x86_64-gnu-linux.mt_alloc/share
--- Comment #4 from redi at gcc dot gnu dot org 2010-09-14 12:47 ---
looks sensible, I'll do that
--
redi at gcc dot gnu dot org changed:
What|Removed |Added
Assi
--- Comment #3 from pluto at agmk dot net 2010-09-14 12:04 ---
(In reply to comment #1)
> It's nothing to do with unordered_map, it's std::string, and it fails because
> lazy_string was added in GDB 7.1
>
> we can probably do something like
>
> if (gdb.VERSION == '7.0'):
>
--- Comment #2 from redi at gcc dot gnu dot org 2010-08-25 14:17 ---
Tom, I don't remember if the decision to use lazy_string (and therefore require
GDB 7.1) was intentional - is a fallback worthwhile?
--
redi at gcc dot gnu dot org changed:
What|Removed
13 matches
Mail list logo