This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug gdb/21829] New: GDB internal error: Assertion `name[prefix_len + 1] == ':'' failed.


https://sourceware.org/bugzilla/show_bug.cgi?id=21829

            Bug ID: 21829
           Summary: GDB internal error: Assertion `name[prefix_len + 1] ==
                    ':'' failed.
           Product: gdb
           Version: 7.11.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: vivekrane at gmail dot com
  Target Milestone: ---

When debugging TensorFlow on UBuntu, stopped at a breakpoint, trying to call a
function that pretty prints the object, this error often shows up. Here's the
text from my console:

Thread 1 "python" hit Breakpoint 12, tensorflow::DFS(tensorflow::Graph const&,
std::function<void (tensorflow::Node*)> const&, std::function<void
(tensorflow::Node*)> const&) (g=..., enter=..., leave=...)
    at tensorflow/core/graph/algorithm.cc:34
34        stack.push_back(Work{g.source_node(), false});
(gdb) p g.source_node()->DebugString()
/build/gdb-cXfXJ3/gdb-7.11.1/gdb/cp-namespace.c:252: internal-error:
cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':''
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:
<http://www.gnu.org/software/gdb/bugs/>.

/build/gdb-cXfXJ3/gdb-7.11.1/gdb/cp-namespace.c:252: internal-error:
cp_search_static_and_baseclasses: Assertion `name[prefix_len + 1] == ':''
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]