Hi,
> so if I believe the debugger, there is a bug in the
> thread-safe version of our C-library, but I don't dare to make such a
statement about the
> million-times-used glibc version 2.2.5 ...
This could well be a glibc problem.
Are you linking statically or dynamically?
There was a definite problem with static builds and some versions of
glibc discussed in tech-talk, starting on July 31, 2003. Thread was
"Problem with static build on Linux". I was getting strange errors like
yours in commonly used libraries and functions, e.g.:
"I have tested the static image on another Linux system and it sometimes
fails in nss_getline() as one the other system, but it sometimes fails
in __current_locale_name() instead."
My resolution to the problem was to upgrade glibc:
"Following up on suggestions here earlier today I upgraded all of the
glibc packages on my Redhat 8 machine to the latest versions from
Redhat. It does indeed fix the problem, and I can now build
applications statically that run fine.
sonata> rpm -qa | grep glibc
glibc-debug-2.3.2-4.80.6
glibc-2.3.2-4.80.6
glibc-devel-2.3.2-4.80.6
glibc-common-2.3.2-4.80.6
glibc-profile-2.3.2-4.80.6
glibc-kernheaders-2.4-7.20
glibc-utils-2.3.2-4.80.6
glibc-debug-static-2.3.2-4.80.6 "
Mark Rivers
- Replies:
- RE: sequencer SEGV Benjamin Sailer
- Navigate by Date:
- Prev:
RE: sequencer SEGV Nick Rees
- Next:
close_record ? Amy Baum
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: sequencer SEGV Nick Rees
- Next:
RE: sequencer SEGV Benjamin Sailer
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
<2003>
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|