[Python-bugs-list] [ python-Bugs-727051 ] valgrind python fails

SourceForge.net noreply@sourceforge.net
Tue, 29 Apr 2003 12:06:59 -0700


Bugs item #727051, was opened at 2003-04-24 17:49
Message generated for change (Comment added) made by arigo
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=727051&group_id=5470

Category: Python Interpreter Core
Group: Python 2.3
Status: Open
Resolution: None
Priority: 5
Submitted By: Ralf W. Grosse-Kunstleve (rwgk)
Assigned to: Nobody/Anonymous (nobody)
Summary: valgrind python fails

Initial Comment:
Platform:
  Redhat 7.3 on Intel Xeon

Packages involved:
  valgrind-1.9.5 (http://developer.kde.org/~sewardj/)
  Python CVS snapshot Thu Apr 24 10:00:00 PDT 2003

valgrind python fails with the following message:

% valgrind python
python: relocation error: /lib/librt.so.1: symbol 
__pthread_clock_settime, version GLIBC_PRIVATE not 
defined in file libpthread.so.0 with link time reference

This is with:

% python
Python 2.3b1 (#1, Apr 24 2003, 10:20:26) 
[GCC 2.96 20000731 (Red Hat Linux 7.3 2.96-113)] on 
linux2
Type "help", "copyright", "credits" or "license" for more 
information.
>>> 

I observed the same problem with Python 2.3a2.

There are no problems when using Python 2.2.1 on the 
exact same platform with the same valgrind installation.


----------------------------------------------------------------------

Comment By: Armin Rigo (arigo)
Date: 2003-04-29 19:06

Message:
Logged In: YES 
user_id=4771

This is documented as a known problem with the librt.so
library on http://developer.kde.org/~sewardj/docs-1.9.5/FAQ.txt.

What I cannot understand is the purpose of binding against
that library on Linux. It ends up in the Makefile for some
indirect reason. I tried without it and the 'make test'
works just fine.

Is it worth any further investigation ? If not, close this
bug track.

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2003-04-24 19:14

Message:
Logged In: YES 
user_id=33168

I think I got around this problem by adding:

  void __pthread_clock_settime() { }

I think this may be mentioned in the valgrind FAQ/doc.  Or
perhaps, it's something similar which I am confusing.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=727051&group_id=5470