[RFC] Debug Methods in GDB Python

Siva Chandra sivachandra@google.com
Sat Nov 16 02:48:00 GMT 2013


On Fri, Nov 15, 2013 at 4:53 PM, Siva Chandra <sivachandra@google.com> wrote:
> On Fri, Nov 15, 2013 at 4:05 PM, Doug Evans <dje@google.com> wrote:
>> I could be wrong but it seemed like errors were handled differently
>> than in the pretty-printers.
>> The inconsistency doesn't feel warranted.
>
> Yes, there is a difference.

Sorry, sent the last mail without completing my response here.

So, yes there is a difference. But as I explained, I did it that way
because, in my opinion we should not stop as soon as we hit an error
when looking up for a match from among the Python implementations as
there could be a source language implementation. If there were to be
an error invoking a Python implementation, then that is reported via
the relevant functions in valarith.c. All other Python errors are
reported but do not stop GDB from proceeding to evaluate expressions.



More information about the Gdb-patches mailing list