Hi, I used
sudo debuginfo-install firefox
To get the debugging packages necessary to run firefox from within gdb and get some meaningful stack trace output - see http://bugs.centos.org/view.php?id=3258
To make this work properly, I installed the 'debuginfo-repo' like this:
more /etc/yum.repos.d/debuggery.repo [debuggery] name=CentOS-$releasever - DebugInfo baseurl=http://debuginfo.centos.org/$releasever/$basearch/ priority=1
However, it seems there is a problem with the pango package in that repo, because when I fire up firefox within gdb I get the following warnings:
(gdb) run -P "Local Disk" Starting program: /usr/lib/firefox-3.0.4/firefox -P "Local Disk" (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208387888 (LWP 7595)] warning: the debug information found in "/usr/lib/debug//usr/lib/libpangocairo-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangocairo-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpangoft2-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangoft2-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpango-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpango-1.0.so.0" (CRC mismatch).
[New Thread -1210643568 (LWP 7598)] [New Thread -1221133424 (LWP 7599)] FoxyProxy settingsDir = /local/Scratch/.mozilla/firefox/fcftz9c3.default [New Thread -1231643760 (LWP 7600)] [New Thread -1243612272 (LWP 7601)] [Thread -1243612272 (LWP 7601) exited] [New Thread -1254102128 (LWP 7602)] [Thread -1254102128 (LWP 7602) exited] [New Thread -1254102128 (LWP 7603)] [New Thread -1243612272 (LWP 7604)] [New Thread -1265009776 (LWP 7605)] warning: the debug information found in "/usr/lib/debug//usr/lib/pango/1.5.0/modules/pango-basic-fc.so.debug" does not match "/usr/lib/pango/1.5.0/modules/pango-basic-fc.so" (CRC mismatch).
[Thread -1265009776 (LWP 7605) exited] [New Thread -1265009776 (LWP 7606)] [New Thread -1342178416 (LWP 7607)] ...
This seems strange, because looking at the output of this:
[dbolser@cricket ~]$ yum list installed | grep pango pango.i386 1.14.9-3.el5.centos installed pango-debuginfo.i386 1.14.9-3.el5.centos installed pango-devel.i386 1.14.9-3.el5.centos installed
Seems to suggest that all the package versions match.
Also, for the sake of yum, how come the debuginfo packages do not depend on their version matched package counterpart?
Thanks for any help, and sorry if this is the wrong place to post such a message - please just let me know where I should have sent the email.
All the best,
Dan.
Run rpm --verify on the pango -debuginfo package. If differences are reported, erase and re-install. If no differences, then the pango -debuginfo package was not produced correctly. Note that the CRC check is from gdb & ELF, not from package management.
hth
73 de Jeff
On Nov 21, 2008, at 1:45 PM, Dan Bolser wrote:
Hi, I used
sudo debuginfo-install firefox
To get the debugging packages necessary to run firefox from within gdb and get some meaningful stack trace output - see http://bugs.centos.org/view.php?id=3258
To make this work properly, I installed the 'debuginfo-repo' like this:
more /etc/yum.repos.d/debuggery.repo [debuggery] name=CentOS-$releasever - DebugInfo baseurl=http://debuginfo.centos.org/$releasever/$basearch/ priority=1
However, it seems there is a problem with the pango package in that repo, because when I fire up firefox within gdb I get the following warnings:
(gdb) run -P "Local Disk" Starting program: /usr/lib/firefox-3.0.4/firefox -P "Local Disk" (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208387888 (LWP 7595)] warning: the debug information found in "/usr/lib/debug//usr/lib/libpangocairo-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangocairo-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpangoft2-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangoft2-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpango-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpango-1.0.so.0" (CRC mismatch).
[New Thread -1210643568 (LWP 7598)] [New Thread -1221133424 (LWP 7599)] FoxyProxy settingsDir = /local/Scratch/.mozilla/firefox/ fcftz9c3.default [New Thread -1231643760 (LWP 7600)] [New Thread -1243612272 (LWP 7601)] [Thread -1243612272 (LWP 7601) exited] [New Thread -1254102128 (LWP 7602)] [Thread -1254102128 (LWP 7602) exited] [New Thread -1254102128 (LWP 7603)] [New Thread -1243612272 (LWP 7604)] [New Thread -1265009776 (LWP 7605)] warning: the debug information found in "/usr/lib/debug//usr/lib/pango/1.5.0/modules/pango-basic-fc.so.debug" does not match "/usr/lib/pango/1.5.0/modules/pango-basic-fc.so" (CRC mismatch).
[Thread -1265009776 (LWP 7605) exited] [New Thread -1265009776 (LWP 7606)] [New Thread -1342178416 (LWP 7607)] ...
This seems strange, because looking at the output of this:
[dbolser@cricket ~]$ yum list installed | grep pango pango.i386 1.14.9-3.el5.centos installed pango-debuginfo.i386 1.14.9-3.el5.centos installed pango-devel.i386 1.14.9-3.el5.centos installed
Seems to suggest that all the package versions match.
Also, for the sake of yum, how come the debuginfo packages do not depend on their version matched package counterpart?
Thanks for any help, and sorry if this is the wrong place to post such a message - please just let me know where I should have sent the email.
All the best,
Dan.
-- http://network.nature.com/profile/dan _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
2008/11/21 Jeff Johnson n3npq@mac.com:
Run rpm --verify on the pango -debuginfo package. If differences are reported, erase and re-install. If no differences, then the pango -debuginfo package was not produced correctly. Note that the CRC check is from gdb & ELF, not from package management.
rpm --verify pango pango-debuginfo
no output
Does that show that the pango -debuginfo package was not produced correctly? Who should I bug?
Cheers, Dan.
hth
73 de Jeff
On Nov 21, 2008, at 1:45 PM, Dan Bolser wrote:
Hi, I used
sudo debuginfo-install firefox
To get the debugging packages necessary to run firefox from within gdb and get some meaningful stack trace output - see http://bugs.centos.org/view.php?id=3258
To make this work properly, I installed the 'debuginfo-repo' like this:
more /etc/yum.repos.d/debuggery.repo [debuggery] name=CentOS-$releasever - DebugInfo baseurl=http://debuginfo.centos.org/$releasever/$basearch/ priority=1
However, it seems there is a problem with the pango package in that repo, because when I fire up firefox within gdb I get the following warnings:
(gdb) run -P "Local Disk" Starting program: /usr/lib/firefox-3.0.4/firefox -P "Local Disk" (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208387888 (LWP 7595)] warning: the debug information found in "/usr/lib/debug//usr/lib/libpangocairo-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangocairo-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpangoft2-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpangoft2-1.0.so.0" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libpango-1.0.so.0.1400.9.debug" does not match "/usr/lib/libpango-1.0.so.0" (CRC mismatch).
[New Thread -1210643568 (LWP 7598)] [New Thread -1221133424 (LWP 7599)] FoxyProxy settingsDir = /local/Scratch/.mozilla/firefox/fcftz9c3.default [New Thread -1231643760 (LWP 7600)] [New Thread -1243612272 (LWP 7601)] [Thread -1243612272 (LWP 7601) exited] [New Thread -1254102128 (LWP 7602)] [Thread -1254102128 (LWP 7602) exited] [New Thread -1254102128 (LWP 7603)] [New Thread -1243612272 (LWP 7604)] [New Thread -1265009776 (LWP 7605)] warning: the debug information found in "/usr/lib/debug//usr/lib/pango/1.5.0/modules/pango-basic-fc.so.debug" does not match "/usr/lib/pango/1.5.0/modules/pango-basic-fc.so" (CRC mismatch).
[Thread -1265009776 (LWP 7605) exited] [New Thread -1265009776 (LWP 7606)] [New Thread -1342178416 (LWP 7607)] ...
This seems strange, because looking at the output of this:
[dbolser@cricket ~]$ yum list installed | grep pango pango.i386 1.14.9-3.el5.centos installed pango-debuginfo.i386 1.14.9-3.el5.centos installed pango-devel.i386 1.14.9-3.el5.centos installed
Seems to suggest that all the package versions match.
Also, for the sake of yum, how come the debuginfo packages do not depend on their version matched package counterpart?
Thanks for any help, and sorry if this is the wrong place to post such a message - please just let me know where I should have sent the email.
All the best,
Dan.
-- http://network.nature.com/profile/dan _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Nov 21, 2008, at 2:26 PM, Dan Bolser wrote:
2008/11/21 Jeff Johnson n3npq@mac.com:
Run rpm --verify on the pango -debuginfo package. If differences are reported, erase and re-install. If no differences, then the pango -debuginfo package was not produced correctly. Note that the CRC check is from gdb & ELF, not from package management.
rpm --verify pango pango-debuginfo
no output
you can add -v to see what is/was checked. but no outout == no problem.
Does that show that the pango -debuginfo package was not produced correctly? Who should I bug?
Dunno. Dunno. But a CRC check failure usually means that there is an inconsistency in the plaintext being checked.
73 de Jeff
2008/11/21 Jeff Johnson n3npq@mac.com:
On Nov 21, 2008, at 2:26 PM, Dan Bolser wrote:
2008/11/21 Jeff Johnson n3npq@mac.com:
Run rpm --verify on the pango -debuginfo package. If differences are reported, erase and re-install. If no differences, then the pango -debuginfo package was not produced correctly. Note that the CRC check is from gdb & ELF, not from package management.
rpm --verify pango pango-debuginfo
no output
you can add -v to see what is/was checked. but no outout == no problem.
Does that show that the pango -debuginfo package was not produced correctly? Who should I bug?
Dunno. Dunno. But a CRC check failure usually means that there is an inconsistency in the plaintext being checked.
Who maintains the repo?
73 de Jeff
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
2008/11/26 Karanbir Singh mail-lists@karan.org:
Dan Bolser wrote:
Who maintains the repo?
Which repo ? All centos published binaries have src.rpm's to match, should not be hard to find and reproduce, patches along with some commentary on why, always welcome.
I meant this repo:
more /etc/yum.repos.d/debuggery.repo [debuggery] name=CentOS-$releasever - DebugInfo baseurl=http://debuginfo.centos.org/$releasever/$basearch/ priority=1
Can you explain what you mean above "find and reproduce"?
Cheers,
- KB
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
Dan Bolser wrote:
packages there come from the centos buildsystem.
Can you explain what you mean above "find and reproduce"?
the src.rpm used to build the binary, and the debuginfo packages are published at mirror.centos.org, you should be able to grab that, build and reproduce / check the issues.
- KB
2008/11/27 Karanbir Singh mail-lists@karan.org:
Dan Bolser wrote:
packages there come from the centos buildsystem.
Can you explain what you mean above "find and reproduce"?
the src.rpm used to build the binary, and the debuginfo packages are published at mirror.centos.org, you should be able to grab that, build and reproduce / check the issues.
Firefox keeps crashing, and I was told to do a back trace in gdb ... Other than that I don't know what I am doing.
Thanks for replying though, Dan.
- KB
CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Nov 27, 2008, at 9:14 AM, Dan Bolser wrote:
Firefox keeps crashing, and I was told to do a back trace in gdb ... Other than that I don't know what I am doing.
If all you need is a firefox backtrace, you can likely achieve that in spite of pango symbols having CRC errors.
Fixing pango -debuginfo is likely considerably harder than getting a firefox backtrace.
73 de Jeff
-
Dan Bolser -
Jeff Johnson -
Karanbir Singh