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/14373] std::vector


http://sourceware.org/bugzilla/show_bug.cgi?id=14373

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2012-07-20 19:45:24 UTC ---
First, I agree it would be good to be able to interrupt
gdb when it gets wedged like this.

However, the problem here is that the varobj has
many children -- in my test, 105312 of them (but obviously
YMMV).

Front ends are supposed to limit dynamic varobj output
using the provided controls, like -var-set-update-range
or the optional arguments to -var-list-children.
Otherwise, bad things will happen.

In this case, the vector is uninitialized, causing problems.
But the same problems can occur due to other bugs in the program
(trashing the heap), or just if the program happens to create
a really huge data structure -- not unheard-of.

-- 
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.


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