From: Tom Tromey <tromey@redhat.com>
To: pmuldoon@redhat.com
Cc: Hui Zhu <hui_zhu@mentor.com>,
gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make "backtrace" doesn't print python stack if init python dir get fail
Date: Wed, 15 Jan 2014 20:06:00 -0000 [thread overview]
Message-ID: <87ppntovr9.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20140114213218.GA24832@localhost.localdomain> (Phil Muldoon's message of "Tue, 14 Jan 2014 21:32:18 +0000")
>>>>> "Phil" == Phil Muldoon <pmuldoon@redhat.com> writes:
Phil> I think the suggestion in the warning text is still good though?
Yeah, good point.
>> I lean toward the simpler solution of changing the warning message and
>> clearing the flag.
Phil> I think so too, it makes things simpler for the user. But in this
Phil> patch you deleted the warning, so not sure if the patch you posted is
Phil> your preferred solution?
No, the patch left the message there. I looked again just now to make
sure :)
Tom
prev parent reply other threads:[~2014-01-15 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 17:35 Hui Zhu
2013-12-02 16:05 ` Tom Tromey
2013-12-03 7:30 ` Hui Zhu
2013-12-03 20:27 ` Tom Tromey
2013-12-04 7:41 ` Hui Zhu
2013-12-11 17:07 ` Tom Tromey
2013-12-13 11:49 ` Hui Zhu
2014-01-14 16:09 ` Tom Tromey
2014-01-14 17:41 ` Tom Tromey
2014-01-14 21:32 ` Phil Muldoon
2014-01-15 20:06 ` 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=87ppntovr9.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--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