This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug python/14373] std::vector
- From: "tromey at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 25 Jul 2012 15:36:43 +0000
- Subject: [Bug python/14373] std::vector
- Auto-submitted: auto-generated
- References: <bug-14373-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14373
--- Comment #3 from Tom Tromey <tromey at redhat dot com> 2012-07-25 15:36:43 UTC ---
(In reply to comment #2)
> I agree to you that it is better to set an update range, also for the other
> cases you mentioned. However is there no possibility to check if the variable
> is unitialized, or do you know if a feature like that will be implemented in
> future? Eventually from gcc perspective.
It may be possible to do this in gcc -- there was one attempt already, see
DW_OP_GNU_uninit -- but I think it is not a good approach, for the reasons
already outlined.
--
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.