On 15/12/16 18:29 +, Jonathan Wakely wrote:
On 15/12/16 13:11 -0500, David Malcolm wrote:
BTW, is it always a ValueError exception?
(I'm a little wary of naked "except:" in Python, as it can catch
*anything*, including syntax errors in the try/except-guarded code).
Good point. As far as I
On 15/12/16 13:11 -0500, David Malcolm wrote:
On Thu, 2016-12-15 at 17:39 +, Jonathan Wakely wrote:
This patch tries to improve the user experience when debugging
container iterators, for cases where some of the typedefs used by the
printers are not in the debuginfo, so gdb.lookup_type() cal
On Thu, 2016-12-15 at 17:39 +, Jonathan Wakely wrote:
> This patch tries to improve the user experience when debugging
> container iterators, for cases where some of the typedefs used by the
> printers are not in the debuginfo, so gdb.lookup_type() calls fail.
> That happens if the iterator's o
On 15 December 2016 at 19:39, Jonathan Wakely wrote:
> This patch tries to improve the user experience when debugging
> container iterators, for cases where some of the typedefs used by the
> printers are not in the debuginfo, so gdb.lookup_type() calls fail.
> That happens if the iterator's opera
This patch tries to improve the user experience when debugging
container iterators, for cases where some of the typedefs used by the
printers are not in the debuginfo, so gdb.lookup_type() calls fail.
That happens if the iterator's operator*() and operator->() haven't
been instantiated, or if they
