From: Peter Seebach <peter.seebach@windriver.com>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: pseudo interaction issue
Date: Thu, 22 Mar 2012 21:29:37 -0500 [thread overview]
Message-ID: <20120322212937.71b9bf28@wrlaptop> (raw)
In-Reply-To: <1332464476.1849.23.camel@dongxiao-osel>
On Fri, 23 Mar 2012 09:01:16 +0800
"Xu, Dongxiao" <dongxiao.xu@intel.com> wrote:
> I think the difference between Hob and other UI (e.x., knotty) is
> that, when building image is finished in knotty, the UI, bitbake
> server, and pseudo all quit. But in Hob, everything still alive after
> a build. I noticed that the pseudo error happens only when Hob is
> trying to issue a second build.
I get it on the first build.
... You see the issue.
Pseudo shouldn't be having a problem, it's designed to restart as
needed.
Right now, what I know is:
1. I didn't catch popen(), and this can actually be an issue with
stuff like PSEUDO_UNLOAD or PSEUDO_DISABLED in play.
2. If I wrap popen, and have the wrapper unconditionally emit a
diagnostic, that works for simple os.popen() test cases.
3. But not for the case that's triggering this.
So it looks like, when this runs, we have a Python session which has
had pseudo unloaded, not just disabled, which then sets LD_PRELOAD but
doesn't set PSEUDO_PREFIX. Or something.
I'm still trying to get better data on this, like figure out how the
sub-process is even getting invoked.
-s
--
Listen, get this. Nobody with a good compiler needs to be justified.
next prev parent reply other threads:[~2012-03-23 2:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 17:35 pseudo interaction issue Paul Eggleton
2012-02-17 18:50 ` Mark Hatle
2012-03-14 9:02 ` Xu, Dongxiao
2012-03-22 1:49 ` Xu, Dongxiao
2012-03-22 16:18 ` Peter Seebach
2012-03-23 1:01 ` Xu, Dongxiao
2012-03-23 2:29 ` Peter Seebach [this message]
2012-03-23 3:21 ` Xu, Dongxiao
2012-03-23 7:16 ` Peter Seebach
2012-03-23 12:20 ` Paul Eggleton
2012-03-23 20:06 ` Peter Seebach
2012-03-23 22:45 ` Peter Seebach
2012-03-24 17:15 ` Richard Purdie
2012-03-24 17:41 ` Richard Purdie
2012-03-26 16:44 ` Peter Seebach
2012-03-26 16:47 ` Richard Purdie
2012-03-26 17:18 ` Peter Seebach
2012-03-26 21:45 ` Richard Purdie
2012-03-27 3:47 ` Peter Seebach
2012-03-27 14:26 ` Peter Seebach
2012-03-26 7:43 ` Peter Seebach
2012-03-26 9:23 ` Richard Purdie
2012-03-26 20:36 ` Peter Seebach
2012-03-26 20:41 ` Peter Seebach
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=20120322212937.71b9bf28@wrlaptop \
--to=peter.seebach@windriver.com \
--cc=dongxiao.xu@intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.