public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andreasheimberger at gmx dot at" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/14373] New: std::vector
Date: Thu, 19 Jul 2012 11:33:00 -0000 [thread overview]
Message-ID: <bug-14373-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14373
Bug #: 14373
Summary: std::vector
Product: gdb
Version: 7.4
Status: NEW
Severity: normal
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: andreasheimberger@gmx.at
Classification: Unclassified
Created attachment 6537
--> http://sourceware.org/bugzilla/attachment.cgi?id=6537
vector gdb frozen
Having an unitialized std::vector gdb freezes and doesn't respond anyway.
Especially when you call -var-list-children in the line where std::vector is
still uninitialized.
Example:
Code GDB
------------------------------------------------------------------------------
std::vector<int> vec; << -var-create - * vec
<< -var-list-children var1
vec.push_back(1);
-------------------------------------------------------------------------------
Within Eclipse CDT they must have some implementation that debugging is still
available.
--
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:[~2012-07-19 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 11:33 andreasheimberger at gmx dot at [this message]
2012-07-20 19:45 ` [Bug python/14373] std::vector tromey at redhat dot com
2012-07-23 8:22 ` andreasheimberger at gmx dot at
2012-07-25 15:36 ` tromey at redhat dot com
2022-06-05 15:04 ` tromey 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-14373-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: link
Be 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).