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 python/16470] Crash when inspecting STL containers with GDB pretty print


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

--- Comment #2 from Jan Pohanka <xhpohanka at gmail dot com> ---
I can also reproduce this bug using Axel's steps. 

This is the content of my ~/.gdbinit

add-auto-load-safe-path /home/honza/dev

python
import sys
sys.path.insert(0, '/home/honza/dev/gdb-pretty')
from libstdcxx.v6.printers import register_libstdcxx_printers
register_libstdcxx_printers (None)
end

set print pretty on
set print object on
set print static-members on
set print vtbl on
set print demangle on
set demangle-style gnu-v3

On https://sourceware.org/gdb/wiki/STLSupport there is a description how to get
the pretty printers.

After passing the MI commands to GDB as Axel described, I'm getting following
error

~"/home/zumbi/gdb-7.6.1/gdb/varobj.c:3532: internal-error: c_value_of_variable:
Assertion `!value_lazy (var->value)' failed.\nA problem internal to GDB has
been detected,\nfurther debugging may prove unreliable.\nQuit this debugging
session? "
~"(y or n) "
n
~"/home/zumbi/gdb-7.6.1/gdb/varobj.c:3532: internal-error: c_value_of_variable:
Assertion `!value_lazy (var->value)' failed.\nA problem internal to GDB has
been detected,\nfurther debugging may prove unreliable.\nCreate a core file of
GDB? "
~"(y or n) "
n
^error,msg="unknown error"
(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]