Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Tony Wang <wangzheyu1989@gmail.com>, yunlian@chromium.org
Subject: Re: Is python dependency detection acceptable?
Date: Wed, 06 Aug 2014 02:12:00 -0000	[thread overview]
Message-ID: <1490951.iZjJNAbgyO@vapier> (raw)
In-Reply-To: <CA+G=Tw1oO6qX=cY7s6PQ-3Apj_wc0RAbdAnPV1zpREE8sEYpOw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]

On Tue 24 Jun 2014 10:48:05 Tony Wang wrote:
> Recently I'm building gdb with python support, and I noticed that gdb
> with python support will heavily depends on the python environment on
> the build machine.
> 
> So if I give the gdb with python support to other PC, and the python
> environment is different from my build machine, the gdb will fail to
> launch. Basically, I think python support is not wanted by every user,
> but it's a little bit confusing for toolchain maintainer to release
> two version of gdb(with and without python). So is it possible to
> detect in the gdb, whether the user python environment is ok?(Usually
> user will have python, but the library path or version may cause the
> gdb fail to launch). If the user do not have the python, then just
> disable python function in gdb.
> 
> I've noticed a hack patch to do this before, it just test the pyinit
> function in a new thread to see if the python environment is ready. Is
> such a operation acceptable?

this is how we addressed it in CrOS:
https://chromium.googlesource.com/chromiumos/third_party/gdb/+/b35e9f2915f319ed23e50d66c5d157370e113317%5E%21/

we had to do this for the same reason you describe -- we build gdb in one env  
(Gentoo) and deploy it in another (Ubuntu), and the two have different pythons 
available.  python works fine in the original env and we want to keep it 
viable, but we don't want gdb killing itself simply because python isn't 
available.

hopefully Yunlian will submit the patch for official consideration at some 
point :).
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      reply	other threads:[~2014-08-06  2:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  2:48 Tony Wang
2014-08-06  2:12 ` Mike Frysinger [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=1490951.iZjJNAbgyO@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb@sourceware.org \
    --cc=wangzheyu1989@gmail.com \
    --cc=yunlian@chromium.org \
    /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