Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCHv2] package/kodi: needs .py modules
Date: Sun, 20 Sep 2015 10:17:01 +0200	[thread overview]
Message-ID: <20150920101701.60fc27ad@free-electrons.com> (raw)
In-Reply-To: <20150919154735.GA3613@free.fr>

Hello,

On Sat, 19 Sep 2015 17:47:35 +0200, Yann E. MORIN wrote:

> > There is some logic in Kodi that tries to set the PYTHONHOME
> > environment variable. Can you see in the logs if you see the following
> > messages (from xbmc/interfaces/python/XBPython.cpp) :
> > 
> >   CLog::Log(LOGINFO, "initializing python engine.");
> >   CLog::Log(LOGDEBUG, "PYTHONHOME -> %s", CSpecialProtocol::TranslatePath("special://frameworks").c_str());
> >   CLog::Log(LOGDEBUG, "PYTHONPATH -> %s", CSpecialProtocol::TranslatePath("special://frameworks").c_str());
> 
> No, those messages I did not see. Only the message about suggesting to
> set PYTHONHOME followed by the segfault.

All the messages you posted are coming from Python itself. I'm
interested in seeing under what conditions is Kodi starting the Python
interpreter. But there's lot of code in Kodi, so I'm not sure from
which place the Python interpreter is started and causing the segfault
you're seeing.

Any chance you do a debug symbols enabled build to get a backtrace of
Kodi ?

> > Alternatively, can you change Python, in file Modules/getpath.c,
> > function calculate_path(), and dump all the environment variables?
> 
> Sure, I can have a look at it. No promise, though...

Yes, sure. You could also report a bug in the Kodi bug tracker? They
might at least be able to give some hints about what's going on.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-09-20  8:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 21:13 [Buildroot] [PATCHv2] package/kodi: needs .py modules Yann E. MORIN
2015-09-13 21:29 ` Thomas Petazzoni
2015-09-13 21:35   ` Yann E. MORIN
2015-09-19 12:40     ` Thomas Petazzoni
2015-09-19 15:47       ` Yann E. MORIN
2015-09-20  8:17         ` Thomas Petazzoni [this message]
2015-09-26 14:40   ` Bernd Kuhls
2015-09-15 16:37 ` Arnout Vandecappelle
2015-09-15 20:03   ` Yann E. MORIN
2015-09-15 20:52     ` Arnout Vandecappelle
2015-09-15 21:05       ` Yann E. MORIN
2015-12-05 20:38 ` Yann E. MORIN

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=20150920101701.60fc27ad@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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