This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Debug Methods in GDB Python
- From: Doug Evans <dje at google dot com>
- To: Siva Chandra <sivachandra at google dot com>
- Cc: Tom Tromey <tromey at redhat dot com>, gdb-patches <gdb-patches at sourceware dot org>
- Date: Tue, 19 Nov 2013 15:52:24 -0800
- Subject: Re: [RFC] Debug Methods in GDB Python
- Authentication-results: sourceware.org; auth=none
- References: <CAGyQ6gyKTCdcjMcbfnc4zV3+yEt9tCTJzS8eW92dQrQzikRaTQ at mail dot gmail dot com> <CAGyQ6gxzG8vuPyFKHpacHS7W7jMEReidWDBkNJjywOXADXgVnw at mail dot gmail dot com> <87r4hefx59 dot fsf at fleche dot redhat dot com> <CAGyQ6gw_-MOu4Y9D+mUf-A55_Ms+j9JAmM9dU0y8PdJw73EkNw at mail dot gmail dot com> <871u995pbt dot fsf at fleche dot redhat dot com> <CAGyQ6gywGMDwmm9fHpPGhwE9vrki1VE8uDM2hRFEAvCZKaTyJg at mail dot gmail dot com> <87ehaq5nkr dot fsf at fleche dot redhat dot com> <CAGyQ6gwT5+Jmu4bqgakjCWmmZtWjbd83n0qq=B9ctfWjv7oS_w at mail dot gmail dot com> <87txfds4vf dot fsf at fleche dot redhat dot com> <CAGyQ6gzaht0KYTxdFFZDeAo5hxesOmjCAiVomX8d_eV4XGK_CQ at mail dot gmail dot com> <CADPb22TgkC-KBhAoYvNBueOKrHAFWwvd9TgYaQ2=Oq5qsFoZrA at mail dot gmail dot com> <CAGyQ6gwtj3TEazHJYvVNwbZnN3hh6ZJD_dcG4spZ56hkXaP2ag at mail dot gmail dot com> <CAGyQ6gz_vh+0inCVOh1tWuMNvQ+tYbLjPatDCKLUB=yrD=JYOA at mail dot gmail dot com>
On Fri, Nov 15, 2013 at 5:03 PM, Siva Chandra <sivachandra@google.com> wrote:
> 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.
Ah.
I can imagine scenarios where I would not want gdb to continue anyway,
though I'm not sure they're important enough to worry about now.