This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] PR python/12438
- From: Kevin Pouget <kevin dot pouget at gmail dot com>
- To: pmuldoon at redhat dot com, Tom Tromey <tromey at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 17 Oct 2011 14:49:02 +0200
- Subject: Re: [patch] PR python/12438
- References: <m31uyblkwj.fsf@redhat.com>
On Thu, Jun 30, 2011 at 11:37 AM, Phil Muldoon <pmuldoon@redhat.com> wrote:
>
> This patch addresses bug PR python/12438. ?Mark - and other users - have
> asked that maint set python print-stack is off by default. ?This makes
> sense to me, as while stack-traces are useful, they can impact
> readability of GDB output. ?Python developers can always turn it back on
> again.
Hello,
I have a question regarding this patch, which was committed at the end of June,
wouldn't GDB let the user know, one way or an other, that there was
something wrong happened ?
when you run a command, and see to "warning/error" message, you expect
that everything went right, but that's not true when this flag is set,
is it?
I don't know if Python allows to do it, but i think it would be nice
to see something like:
> NameError: global name 'comp' is not define
which is the last line of a python stacktrace
Thanks,
Kevin