public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "genpfault at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug varobj/15166] New: varobj.c:3871: internal-error: cplus_describe_child: Assertion `access' failed. Date: Thu, 21 Feb 2013 03:46:00 -0000 [thread overview] Message-ID: <bug-15166-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=15166 Bug #: 15166 Summary: varobj.c:3871: internal-error: cplus_describe_child: Assertion `access' failed. Product: gdb Version: 7.5 Status: NEW Severity: normal Priority: P2 Component: varobj AssignedTo: unassigned@sourceware.org ReportedBy: genpfault@gmail.com Classification: Unclassified Created attachment 6884 --> http://sourceware.org/bugzilla/attachment.cgi?id=6884 Test program Trying to use the Python pretty-printers on a std::map causes gdb to error out with: varobj.c:3871: internal-error: cplus_describe_child: Assertion `access' failed. Environment/test sequence: Running up-to-date Debian Wheezy (amd64). $ uname -a: Linux genpfault 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux $ gdb GNU gdb (GDB) 7.5.50.20130219 Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. $ g++ -v Using built-in specs. COLLECT_GCC=g++ COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.7/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 4.7.2-5' --with-bugurl=file:///usr/share/doc/gcc-4.7/README.Bugs --enable-languages=c,c++,go,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.7 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.7 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --with-arch-32=i586 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.7.2 (Debian 4.7.2-5) # main.cpp is attached. # Distro-shipped pretty-printers used by script.txt are attached. # output.txt is attached. $ g++ -g main.cpp -o main $ gdb -nx --interpreter=mi2 ./main < script.txt > output.txt -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2013-02-21 3:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-21 3:46 genpfault at gmail dot com [this message] 2013-02-21 3:46 ` [Bug varobj/15166] " genpfault at gmail dot com 2013-02-21 3:47 ` genpfault at gmail dot com 2013-02-21 3:48 ` genpfault at gmail dot com 2013-02-21 21:58 ` genpfault at gmail dot com 2013-03-16 6:05 ` genpfault at gmail dot com 2013-06-26 1:50 ` genpfault at gmail dot com 2024-01-13 18:53 ` ssbssa at sourceware dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-15166-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).