Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Pouget <kevin.pouget@gmail.com>
To: pmuldoon@redhat.com, Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] PR python/12438
Date: Mon, 17 Oct 2011 13:00:00 -0000	[thread overview]
Message-ID: <CAPftXULe+rz_KdjYCjyNE3u0RVJg6yL4hV300WXO+khA49zG1w@mail.gmail.com> (raw)
In-Reply-To: <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


  parent reply	other threads:[~2011-10-17 12:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  9:38 Phil Muldoon
2011-06-30 19:58 ` Tom Tromey
2011-07-07 16:16   ` Phil Muldoon
2011-07-07 18:47     ` Eli Zaretskii
2011-07-07 18:52     ` Tom Tromey
2011-07-11 17:16       ` Phil Muldoon
2011-10-17 13:00 ` Kevin Pouget [this message]
2011-10-17 13:49   ` Phil Muldoon
2011-10-19 20:56   ` Tom Tromey
2011-10-20 12:33     ` Phil Muldoon
2011-10-21  9:43     ` Kevin Pouget

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=CAPftXULe+rz_KdjYCjyNE3u0RVJg6yL4hV300WXO+khA49zG1w@mail.gmail.com \
    --to=kevin.pouget@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pmuldoon@redhat.com \
    --cc=tromey@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