From: Tom Tromey <tromey@redhat.com>
To: Michel METZGER <michel.metzger@st.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Python API - gdb.GdbError in convenience functions
Date: Fri, 04 Mar 2011 21:22:00 -0000 [thread overview]
Message-ID: <m3d3m6r36g.fsf@fleche.redhat.com> (raw)
In-Reply-To: <5B4CE209869C6A4797F5FAA0B348F0A0D9F167BA20@SAFEX1MAIL1.st.com> (Michel METZGER's message of "Fri, 4 Mar 2011 21:52:26 +0100")
>>>>> "Michel" == Michel METZGER <michel.metzger@st.com> writes:
Michel> I need to signal an error in a convenience functions and tried
Michel> to raise a GdbError exception. Unfortunately, contrary to the
Michel> behavior whit a command, the stack trace is displayed. Is it
Michel> the expected behavior ? Is there a way to abort the execution
Michel> of a command that calls a convenience function without a stack
Michel> trace ?
I think what you want sounds good. The only blocker is somebody
actually writing the patch.
Tom
prev parent reply other threads:[~2011-03-04 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 20:53 Michel METZGER
2011-03-04 21:22 ` 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=m3d3m6r36g.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=michel.metzger@st.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