From: Siva Chandra <sivachandra@google.com>
To: Doug Evans <dje@google.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [RFC] Debug Methods in GDB Python
Date: Sat, 16 Nov 2013 02:48:00 -0000 [thread overview]
Message-ID: <CAGyQ6gz_vh+0inCVOh1tWuMNvQ+tYbLjPatDCKLUB=yrD=JYOA@mail.gmail.com> (raw)
In-Reply-To: <CAGyQ6gwtj3TEazHJYvVNwbZnN3hh6ZJD_dcG4spZ56hkXaP2ag@mail.gmail.com>
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.
next prev parent reply other threads:[~2013-11-16 1:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 21:22 Siva Chandra
2013-01-29 1:51 ` Siva Chandra
2013-02-25 23:02 ` Siva Chandra
2013-05-10 19:33 ` Tom Tromey
2013-05-10 19:55 ` Siva Chandra
2013-05-14 19:33 ` Tom Tromey
2013-06-17 19:10 ` Siva Chandra
2013-07-22 20:47 ` Tom Tromey
2013-11-12 2:56 ` Siva Chandra
2013-11-15 22:28 ` Tom Tromey
2013-11-16 0:05 ` Siva Chandra
2013-11-16 0:54 ` Doug Evans
2013-11-16 1:03 ` Siva Chandra
2013-11-16 2:48 ` Siva Chandra [this message]
2013-11-20 0:03 ` Doug Evans
2013-11-19 23:52 ` Doug Evans
2013-11-20 0:39 ` Siva Chandra
2013-11-20 2:48 ` Doug Evans
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGyQ6gz_vh+0inCVOh1tWuMNvQ+tYbLjPatDCKLUB=yrD=JYOA@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox