summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2006-12-12 22:56:00 +0000
committerKen Raeburn <raeburn@mit.edu>2006-12-12 22:56:00 +0000
commit9a330f1f3f1c678a5f6baae7126f53b5efa027ee (patch)
tree06704212dc767cb8db299eb8ea4c9a8fb140b84c
parent4dd8730d2b4827bb00e42df3d656046904269a07 (diff)
downloadkrb5-9a330f1f3f1c678a5f6baae7126f53b5efa027ee.tar.gz
krb5-9a330f1f3f1c678a5f6baae7126f53b5efa027ee.tar.xz
krb5-9a330f1f3f1c678a5f6baae7126f53b5efa027ee.zip
a little more info on libpython loading issue
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@18941 dc483132-0cff-0310-8789-dd5450dbe970
-rw-r--r--src/plugins/locate/python/py-locate.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/plugins/locate/python/py-locate.c b/src/plugins/locate/python/py-locate.c
index 948e028183..37342ac7ae 100644
--- a/src/plugins/locate/python/py-locate.c
+++ b/src/plugins/locate/python/py-locate.c
@@ -44,6 +44,12 @@
logical -- in fact, I'd be concerned if it were otherwise. But not
obvious if you're not thinking about it.
+ Actually, sometimes even with delayed initialization it could be a
+ problem.
+
+ You may be able to work around it with something like:
+ % env LD_PRELOAD=/usr/lib/libpython2.3.so.1.0 kinit ...blah...
+
This module seems rather sensitive to bugs in the Python code. If
it's not correct, you may get core dumps, Python GC errors, etc.
Probably more signs of bugs in this code.