Re: RFC: fix PR 14386

[Tom Tromey <tromey@redhat.com>]

>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:

Phil> It seems we wind-up printing two errors if the value returned to
Phil> "children" is not an iterator.  The "type error" exception that is
Phil> printed with gdbpy_print_stack, and then the explicit error call we call
Phil> right after.  Not sure if this is because of an MI detail needing an
Phil> "error" call, but it seems counter-intuitive to print two error
Phil> messages for one exception.  Maybe in a future patch we could extract
Phil> the exception message from the exception and pass that to the GDB
Phil> error call, or skip the error call completely.

There's PR 12174, which is about this.  The basic problem is that the
exception conversion process is not loss-less.  This is fixable by
adding a bit of state to gdb exceptions, and a little hacking here and
there; but nobody has attempted it comprehensively yet.

Tom