From: Yao Qi <qiyaoltc@gmail.com>
To: Jim Chen <nchen@mozilla.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Specify python2 or python3 as Python program name
Date: Thu, 12 May 2016 12:50:00 -0000 [thread overview]
Message-ID: <867fezcueh.fsf@gmail.com> (raw)
In-Reply-To: <1463003507-13094-1-git-send-email-nchen@mozilla.com> (Jim Chen's message of "Wed, 11 May 2016 17:51:46 -0400")
Jim Chen <nchen@mozilla.com> writes:
> When initializing Python, GDB hard codes the Python program name to
> $prefix/bin/python, where $prefix is /usr for example. On some
> platforms, /usr/bin/python points to python3. So what happens is, even
> if GDB is built with python2 support, GDB ends up setting the Python
> program name to point to python3, causing a mismatch. I think it's
I agree that is a problem ...
> better to deliberately specify python2 or python3.
... but I don't think your patch is the right fix. What we can do in
GDB is probably emit an error if the $prefix/bin/python is incompatible
to the python we build gdb against.
--
Yao (齐尧)
prev parent reply other threads:[~2016-05-12 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 21:54 Jim Chen
2016-05-11 21:54 ` [PATCH] [GDBServer] Send SIGINT using process group ID Jim Chen
2016-05-18 12:10 ` Pedro Alves
2016-05-19 16:01 ` Jim Chen
2016-05-12 5:54 ` [PATCH] Specify python2 or python3 as Python program name Eli Zaretskii
2016-05-12 12:50 ` Yao Qi [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=867fezcueh.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=nchen@mozilla.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