Description of problem: #gdb: GungaDin: I have the following problem: for some reason, gdb doesn't step into a lot of code that's inside header (hpp) or ipp files. 'step' just ends up as 'next' in these cases... any ideas? GungaDin: It happens on Fedora 14. Version-Release number of selected component (if applicable): boost-debuginfo-1.44.0-4.fc14.x86_64 How reproducible: Always. Steps to Reproduce: gdb /usr/lib64/libboost_unit_test_framework-mt.so.1.44.0 Actual results: warning: "/usr/lib/debug/usr/lib64/libboost_unit_test_framework-mt.so.1.44.0.debug": separate debug info file has no debug info Expected results: no warning .debug_* sections. Additional info: .spec uses "RelWithDebInfo", I do not see why it does not work.
I suspect that the following line is the culprit here: -DCMAKE_CXX_FLAGS=-DBOOST_IOSTREAMS_USE_DEPRECATED \ I haven't checked yet, but I'm afraid that that will override the flags, not augment them. All the MPI-enabled libraries are built with debuginfo as they should.
boost-1.44.0-6.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/boost-1.44.0-6.fc14
boost-1.44.0-6.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update boost'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/boost-1.44.0-6.fc14
boost-1.44.0-7.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/boost-1.44.0-7.fc14
boost-1.44.0-7.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
This reintroduces bug #654480. Pleas re-verify.
To be a little more precise (sorry, currently at RoboCup): # rpm -q boost boost-1.44.0-7.fc14.x86_64 # nm /usr/lib/debug/usr/lib64/libboost_iostreams-mt.so.1.44.0.debug | grep file_descriptor_source 000000000000e310 T _ZN5boost9iostreams22file_descriptor_source4openEPKcSt13_Ios_Openmode 000000000000e290 T _ZN5boost9iostreams22file_descriptor_source4openERKNS0_6detail4pathESt13_Ios_Openmode 000000000000e410 T _ZN5boost9iostreams22file_descriptor_source4openERKSsSt13_Ios_Openmode 000000000000ddf0 T _ZN5boost9iostreams22file_descriptor_source4openEiNS0_21file_descriptor_flagsE 000000000000ea10 T _ZN5boost9iostreams22file_descriptor_sourceC1EPKcSt13_Ios_Openmode 000000000000ce00 T _ZN5boost9iostreams22file_descriptor_sourceC1ERKS1_ 000000000000ea70 T _ZN5boost9iostreams22file_descriptor_sourceC1ERKSsSt13_Ios_Openmode 000000000000e8f0 T _ZN5boost9iostreams22file_descriptor_sourceC1EiNS0_21file_descriptor_flagsE 000000000000ea10 T _ZN5boost9iostreams22file_descriptor_sourceC2EPKcSt13_Ios_Openmode 000000000000ce00 T _ZN5boost9iostreams22file_descriptor_sourceC2ERKS1_ 000000000000ea70 T _ZN5boost9iostreams22file_descriptor_sourceC2ERKSsSt13_Ios_Openmode 000000000000e8f0 T _ZN5boost9iostreams22file_descriptor_sourceC2EiNS0_21file_descriptor_flagsE There should be the symbol _ZN5boost9iostreams22file_descriptor_sourceC1Eib, but it isn't. It seems the deprecated functions are not built into Boost anymore. Can you please have a look? Thanks!
The problem was, again, in passing CXXFLAGS. Passing via CMAKE_CXX_FLAGS for some reason breaks when rpm re-quotes the expression as a result of %%{optflags} expansion.
boost-1.44.0-8.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/boost-1.44.0-8.fc14
Package boost-1.44.0-8.fc14: * should fix your issue, * was pushed to the Fedora 14 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing boost-1.44.0-8.fc14' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/boost-1.44.0-8.fc14 then log in and leave karma (feedback).
boost-1.44.0-8.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 697328 has been marked as a duplicate of this bug. ***