[rrd-developers] Seg fault with r1094
rep.dot.nop at gmail.com
Fri Jun 1 19:03:37 CEST 2007
On Fri, Jun 01, 2007 at 11:34:16AM -0500, Matthew Chambers wrote:
>than the debug stuff). How do I do a static build with just configure? And
We would have to add this as an option. I can do this if you like.
>preferably, I want to get the dynamic build working and I'm sure other
>people will too.
Well, dynamic builds work just fine for me :)
>> As i already sent you in private, the one box looks quite suspicious,
>> given that it's RPM database seems to be corrupted, i.e. i wouldn't be
>> convincend anymore that updates work like you'd expect. In general, a
>> box with a broken RPM databse is doomed, in my experience.
>It's actually a pretty fresh install as it is. I don't think the RPM db is
>corrupted. PPC differs from x86 in that Fedora, at least, enjoys installing
>both the PPC and PPC64 versions of many packages, and apparently the RPM -qa
>command you used didn't show that since it didn't list the arch:
>freetype.ppc 2.2.1-16.fc6 installed
>freetype.ppc64 2.2.1-16.fc6 installed
Ah, that would explain it. Ok then and sorry for the false alarm.
>> In my POV trunk is fine on PPC with 32bit (I've even did some cursory
>> checks on an ia64 box to see if there are any unexpected problems on
>> 64bit setups, and all is well) and any other arch for that matter.
>Yes, it seems to be my setup. The code appears to be fine as long as it
>uses the right version of the library. But I'd like to know how to figure
>out which library it's using if it's not using the one that just got
>compiled? And why isn't the dynamic build properly setting up the library
>so that the right one gets used?
>And isn't it also possible that the dynamic build of rrdtool on PPC doesn't
>work whereas a static build does work?
both dynamic as well as static builds work fine.
[building with just CFLAGS="-O0 -g3 -ggdb3" ./configure
--prefix=$HOME/opt" && make install; tar the $HOME/opt up, cp it to the
PPC64 box and..]
[aldot at fenchurch00 ~]$ scp fenchurch1:rrdtool-trunk.installed.tar.bz2 .
ssh: fenchurch1: Name or service not known
[aldot at fenchurch00 ~]$ scp fenchurch01:rrdtool-trunk.installed.tar.bz2 .
aldot at fenchurch01's password:
rrdtool-trunk.installed.tar.bz2 100% 1828KB 1.8MB/s
[aldot at fenchurch00 ~]$ tar -xjf rrdtool-trunk.installed.tar.bz2
[aldot at fenchurch00 ~]$ . opt/rrdtool-trunk.sh
[aldot at fenchurch00 ~]$
[aldot at fenchurch00 ~]$ j=0;for i in
/var/lib/ganglia/rrds/__SummaryInfo__/*.rrd;do rrdtool info $i >
/dev/null || echo "# $i failed";j=$(($j + 1));done; echo "A total of $j
files were info'ed successfully"
A total of 28 files were info'ed successfully
[aldot at fenchurch00 ~]$ echo 'see? all is well, even dynamic builds'
see? all is well, even dynamic builds
[aldot at fenchurch00 ~]$ ldd $(which rrdtool)
linux-vdso32.so.1 => (0x00100000)
librrd.so.2 => /home/aldot/opt//lib/librrd.so.2 (0x0ff30000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x0f830000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0x0f620000)
libz.so.1 => /usr/lib/libz.so.1 (0x0fc80000)
libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0x00380000)
libm.so.6 => /lib/libm.so.6 (0x0fd30000)
libc.so.6 => /lib/libc.so.6 (0xf7e50000)
[aldot at fenchurch00 ~]$ arch
Perhaps check you LD_LIBRARY_PATH, or hit the preloader with a clue bat
or something like this.
More information about the rrd-developers