[opensuse-packaging] debuginfo extraction
Hi, I'm currently investigating an interesting warning I get in one of my packages. I get the following rpm build output for i586 builds: during debuginfo extraction: WARNING: /usr/lib/xulrunner-1.9.2b5/libxpcom.so is already stripped! from rpmlint check: mozilla-xulrunner192.i586: W: unstripped-binary-or-object /usr/lib/xulrunner-1.9.2b5/libxpcom.so in RPM_BUILD_DIR: Hygiea:/var/tmp/build-root/usr/src/packages/BUILD/mozilla/dist/xulrunner # file libxpcom.so libxpcom.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped So everything suggests that the file is created correctly but the debuginfo extraction fails for some reason. Any hints? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Am 20.12.2009 23:00, schrieb Wolfgang Rosenauer:
Hi,
I'm currently investigating an interesting warning I get in one of my packages. I get the following rpm build output for i586 builds:
during debuginfo extraction: WARNING: /usr/lib/xulrunner-1.9.2b5/libxpcom.so is already stripped!
from rpmlint check: mozilla-xulrunner192.i586: W: unstripped-binary-or-object /usr/lib/xulrunner-1.9.2b5/libxpcom.so
in RPM_BUILD_DIR: Hygiea:/var/tmp/build-root/usr/src/packages/BUILD/mozilla/dist/xulrunner # file libxpcom.so libxpcom.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, not stripped
So everything suggests that the file is created correctly but the debuginfo extraction fails for some reason.
additional info: objdump -h libxpcom.so doesn't show any *debug* section (and that's what used in find-debuginfo.sh). I fail to see why though. For compiler experts there are the compiler and linker commandlines below: c++ -o nsXPComStub.o -c -I../../dist/system_wrappers -include ../../config/gcc_hidden.h -DMOZILLA_INTERNAL_API -DOSTYPE=\"Linux2.6\" -DOSARCH=Linux -I./../build -I. -I. -I../../dist/include -I../../dist/include/nsprpub -I/usr/include/nspr4 -I/usr/include/nss3 -fPIC -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long -pedantic -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstac k-protector -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -gstabs+ -fno-strict-aliasing -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -Os -freorder-blocks -fno-reorder-functions -DMOZILLA_CLIENT -include ../../mozilla-config.h -Wp,-MD,.deps/nsXPComStub.pp nsXPComStub.cpp c++ -fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-long-long -pedantic -fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -Os -fno-strict-aliasing -gstabs+ -fno-strict-aliasing -fshort-wchar -pthread -pipe -DNDEBUG -DTRIMMED -Os -freorder-blocks -fno-reorder-functions -fPIC -shared -Wl,-z,defs -Wl,-h,libxpcom.so -o libxpcom.so nsXPComStub.o -lpthread -Wl,-rpath -Wl,/usr/lib/xulrunner-1.9.2b5 -Wl,-rpath-link,/usr/src/packages/BUILD/mozilla/dist/bin -Wl,-rpath-link,/usr/lib -L../../dist/bin -L../../dist/lib -lxul -L/usr/lib -lplds4 -lplc4 -lnspr4 -lpthread -ldl -lasound -ldl -lm Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 20/12/09 19:10, Wolfgang Rosenauer wrote:
-fomit-frame-pointer
"-fomit-frame-pointer This is a very common flag designed to reduce generated code size. It is turned on at all levels of -O (except -O0) on architectures where doing so does not interfere with debugging (such as x86-64), but you may need to activate it yourself by adding it to your flags. Though the GNU gcc manual does not specify all architectures it is turned on by using -O, you will need to explicitly activate it on x86. However, using this flag will make debugging hard to impossible. " -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Sun, Dec 20, 2009 at 07:16:42PM -0300, Cristian Rodríguez wrote:
On 20/12/09 19:10, Wolfgang Rosenauer wrote:
-fomit-frame-pointer
"-fomit-frame-pointer
This is a very common flag designed to reduce generated code size. It is turned on at all levels of -O (except -O0) on architectures where doing so does not interfere with debugging (such as x86-64), but you may need to activate it yourself by adding it to your flags. Though the GNU gcc manual does not specify all architectures it is turned on by using -O, you will need to explicitly activate it on x86. However, using this flag will make debugging hard to impossible. "
It will not stop debuginfo generation. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 20/12/09 19:18, Marcus Meissner wrote:
It will not stop debuginfo generation.
OK , doing a quick search , looks like it is "-gstabs+" which si causing the problem. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On 20/12/09 19:25, Cristian Rodríguez wrote:
On 20/12/09 19:18, Marcus Meissner wrote:
It will not stop debuginfo generation.
OK , doing a quick search , looks like it is "-gstabs+" which si causing the problem.
https://bugzilla.redhat.com/show_bug.cgi?id=488217#c14 -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
participants (3)
-
Cristian Rodríguez -
Marcus Meissner -
Wolfgang Rosenauer