Hide Forgot
(In reply to comment #0) > The GlusterFS RPM packages should be built with debug symbols. Without them it > is impossible to get any information if a crash happens on a production > deployment. > > I don't think it is useful to have a "debuginfo" package like it was done in > earlier versions. It would be better to simply build the default package with > debuginfo. Any sysadmin who really doesn't want the symbols can always strip > them. It seems to be assumed that adding CFLAGS during configure would fix this issue. In fact the rpm flag %{_smp_flags} adds new flags which makes it override the configure default resulting in no debug symbols. Adding CFLAGS="-O0 -g -ggdb" in place of _smp_flags makes it work properly.
The GlusterFS RPM packages should be built with debug symbols. Without them it is impossible to get any information if a crash happens on a production deployment. I don't think it is useful to have a "debuginfo" package like it was done in earlier versions. It would be better to simply build the default package with debuginfo. Any sysadmin who really doesn't want the symbols can always strip them.
Seems like there is another method - Adding following entry to ~/.rpmmacros file %debug_package %{nil} creates binary that's not striped and didn't not create separate debuginfo package. #file /opt/glusterfs/3.2.3qa5/sbin/glusterfsd /opt/glusterfs/3.2.3qa5/sbin/glusterfsd: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, not stripped Will include one of these two methods in version >=3.2.4
Fixed with 3.2.4