From: Kevin Pouget <kevin.pouget@gmail.com>
To: pmuldoon@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [python] [patch] PR python/13329
Date: Wed, 09 Nov 2011 15:49:00 -0000 [thread overview]
Message-ID: <CAPftXU+uOGfbwP_n41P7OHGr6zny1=9UJTpseg4S97g_t8H0Cw@mail.gmail.com> (raw)
In-Reply-To: <m3vcqtmhpc.fsf@redhat.com>
On Wed, Nov 9, 2011 at 4:35 PM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>
> This patch changes the behavior of 'python stack-print' to three modes:
> full, message or none. The default has been set to "message".
>
> full - will print the exception message and the stack.
> message - will print the exception type and message only.
> none - nothing will be printed.
>
> This patch also fixes a bug where we were calling gdbpy_print_stack
> after a few PyRun_SimpleString calls. This is not necessary as that
> API deals with the exception internally and prints its own stack.
>
> This is backwards compatible with the deprecated maint set python print-sack.
>
> on - will set the mode to "full".
> off - will set the mode to "none".
>
> Tested with no regressions.
>
> Cheers,
>
> Phil
>
Thanks Phil, that's exactly what I was looking for :)
just a remark,
+ fprintf_filtered (gdb_stderr,
+ _("Error occurred computing Python error" \
+ "message.\n"));
this error message sounds strange to me, is it correct?
Cheers,
Kevin
next prev parent reply other threads:[~2011-11-09 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 15:36 Phil Muldoon
2011-11-09 15:49 ` Kevin Pouget [this message]
2011-11-09 20:25 ` Phil Muldoon
2011-11-17 20:55 ` Tom Tromey
2011-11-29 13:57 ` Phil Muldoon
2011-12-08 13:08 ` Phil Muldoon
2011-12-13 19:40 ` Tom Tromey
2011-12-15 18:15 ` Phil Muldoon
2011-12-15 21:27 ` Eli Zaretskii
2011-12-16 0:51 ` Tom Tromey
2011-12-16 15:15 ` Phil Muldoon
2011-12-16 15:17 ` Tom Tromey
2011-12-16 17:16 ` Phil Muldoon
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='CAPftXU+uOGfbwP_n41P7OHGr6zny1=9UJTpseg4S97g_t8H0Cw@mail.gmail.com' \
--to=kevin.pouget@gmail.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