[Bug libstdc++/77645] New: Python xmethods tests failing

redi at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Mon Sep 19 13:52:00 GMT 2016


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77645

            Bug ID: 77645
           Summary: Python xmethods tests failing
           Product: gcc
           Version: 7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

Python Exception <class 'gdb.error'> Argument to arithmetic operation not a
number or boolean.: 
deque.gdb:22: Error in sourced command file:
Error while executing Python code.
skipping: Python Exception <class 'gdb.error'> Argument to arithmetic operation
not a number or boolean.: 
skipping: deque.gdb:22: Error in sourced command file:
skipping: Error while executing Python code.
UNSUPPORTED: libstdc++-xmethods/deque.cc

Python Exception <class 'gdb.error'> There is no member or method named
_M_data.: 
list.gdb:13: Error in sourced command file:
Error while executing Python code.
skipping: Python Exception <class 'gdb.error'> There is no member or method
named _M_data.: 
skipping: list.gdb:13: Error in sourced command file:
skipping: Error while executing Python code.
UNSUPPORTED: libstdc++-xmethods/list.cc

Python Exception <class 'gdb.error'> Argument to arithmetic operation not a
number or boolean.: 
skipping: Python Exception <class 'gdb.error'> Argument to arithmetic operation
not a number or boolean.: 
vector.gdb:13: Error in sourced command file:
Error while executing Python code.
skipping: vector.gdb:13: Error in sourced command file:
skipping: Error while executing Python code.
UNSUPPORTED: libstdc++-xmethods/vector.cc


The std::list failure is because the list node has a different structure in
C++11 and later, which is easy to fix.

The deque and vector failures are also related to C++11, but I don't understand
them yet. Pointer arithmetic is failing for a pointer type, maybe because the
code uses a typedef that doesn't look like a pointer.


More information about the Gcc-bugs mailing list