Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: Python pretty-printing [5/6]
Date: Thu, 09 Apr 2009 15:44:00 -0000	[thread overview]
Message-ID: <m3zlepvnld.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1239289186.30578.18.camel@localhost.localdomain> (Thiago Jung Bauermann's message of "Thu\, 09 Apr 2009 11\:59\:45 -0300")

>>>>> "Thiago" == Thiago Jung Bauermann <bauerman@br.ibm.com> writes:

Thiago> I found one potential problem, which could cause the function to return
Thiago> NULL without an exception being set (it's not the case I thought of
Thiago> before, I think): suppose there's no objfile Python object when this
Thiago> function is called, to the ALL_OBJFILES loop will skip all objs, then
Thiago> the gdb module has no pretty_printers attribute, or the pretty_printers
Thiago> value is not a list object. In that case, the function will return NULL
Thiago> without a Python exception being set. Can it happen?

Yes, I see it now:

  /* Fetch the global pretty printer dictionary.  */
  if (! PyObject_HasAttrString (gdb_module, "pretty_printers"))
    goto done;

That is the bad branch.  Thanks.

Also, I think here:

    PyObject *objf = objfile_to_objfile_object (obj);
    if (!objf)
      continue;

... we need to clear the python error.

I will make the needed changes.

Thiago> Also, I noticed that the function may return Py_None if no
Thiago> pretty-printer is found, and the callers even expect that. The function
Thiago> comment needs to be fixed then:

Thanks.

Tom


  parent reply	other threads:[~2009-04-09 15:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-02 20:57 Tom Tromey
2009-04-03 15:29 ` Eli Zaretskii
2009-04-09  0:29   ` Tom Tromey
2009-04-04 16:39 ` Thiago Jung Bauermann
2009-04-09  0:52   ` Tom Tromey
2009-04-09 15:00     ` Thiago Jung Bauermann
2009-04-09 15:19       ` Phil Muldoon
2009-04-09 15:41         ` Thiago Jung Bauermann
2009-04-09 16:18           ` Tom Tromey
2009-04-09 15:44       ` Tom Tromey [this message]
2009-04-09 19:37     ` Tom Tromey
2009-04-09 22:09       ` Thiago Jung Bauermann
2009-04-09 22:36         ` Tom Tromey
2009-04-07 18:32 ` Joel Brobecker
2009-04-07 18:41   ` Tom Tromey
2009-04-07 20:38     ` Joel Brobecker
2009-04-09  1:08 ` Tom Tromey
2009-04-09  7:40   ` Eli Zaretskii
2009-04-09 16:16     ` Tom Tromey
2009-04-09 16:41       ` Eli Zaretskii

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=m3zlepvnld.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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