Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: add python exception subclasses
Date: Fri, 12 Nov 2010 20:47:00 -0000	[thread overview]
Message-ID: <m3iq02qnfw.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3fww2ued0.fsf_-_@fleche.redhat.com> (Tom Tromey's message of	"Tue, 19 Oct 2010 14:17:15 -0600")

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

Tom> This patch implements this idea.  It adds some new subclasses of
Tom> RuntimeError, including one specifically for MEMORY_ERROR.  Then it
Tom> arranges for the memory error exception to be treated specially by the
Tom> pretty-printing code.

I am checking this in now.

I don't think it fully fixes the problem, but it is a good step.

I think the other part is fixing the existing printers so that their
iterators more gracefully handle a MemoryError thrown when computing a
value.

Tom


  parent reply	other threads:[~2010-11-12 20:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CB66700.3000907@gmail.com>
     [not found] ` <m3tykn2id8.fsf@fleche.redhat.com>
2010-10-19 20:17   ` RFA: add python exception subclasses (Was: gdb with python support still get crash on showing uninitialized local variables) Tom Tromey
2010-10-19 21:13     ` Eli Zaretskii
2010-10-20  5:19     ` gdb with python support still get crash on showing uninitialized local variables asmwarrior
2010-10-22 19:13       ` Tom Tromey
2010-10-22 21:22         ` Eli Zaretskii
2010-10-29 19:18           ` Joel Brobecker
2010-10-29 22:01             ` Eli Zaretskii
2010-10-31  2:24               ` asmwarrior
2010-11-12 20:47     ` Tom Tromey [this message]
     [not found]     ` <AANLkTinsJLTZT0ws=LbpYcq85_Z9_R=fcXz+J+kqScJU@mail.gmail.com>
2010-12-17 19:04       ` RFA: add python exception subclasses Tom Tromey
2010-12-18  2:26         ` asmwarrior

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=m3iq02qnfw.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=asmwarrior@gmail.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