From: Tom Tromey <tromey@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch][python] Fix some unguarded GDB calls.
Date: Wed, 20 Mar 2013 17:37:00 -0000 [thread overview]
Message-ID: <87zjxy7z4c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5149E6CF.2050900@redhat.com> (Phil Muldoon's message of "Wed, 20 Mar 2013 16:41:51 +0000")
Tom> Use GDB_PY_HANDLE_EXCEPTION instead.
Phil> Can't as this function returns char *.
Ah, thanks.
No need for that bit then :)
Tom
prev parent reply other threads:[~2013-03-20 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:35 Phil Muldoon
2013-03-20 15:32 ` Tom Tromey
2013-03-20 16:45 ` Phil Muldoon
2013-03-20 17:37 ` Tom Tromey [this message]
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=87zjxy7z4c.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@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