This is the mail archive of the
mailing list for the GDB project.
Re: [python] [patch] PR python/13329
- From: Kevin Pouget <kevin dot pouget at gmail dot com>
- To: pmuldoon at redhat dot com
- Cc: gdb-patches at sourceware dot org
- Date: Wed, 9 Nov 2011 16:48:58 +0100
- Subject: Re: [python] [patch] PR python/13329
- References: <email@example.com>
On Wed, Nov 9, 2011 at 4:35 PM, Phil Muldoon <firstname.lastname@example.org> 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.
Thanks Phil, that's exactly what I was looking for :)
just a remark,
+ fprintf_filtered (gdb_stderr,
+ _("Error occurred computing Python error" \
this error message sounds strange to me, is it correct?