abrt detected a crash. How to reproduce ----- 1. 2. 3. Additional information ====== Attached files ---- backtrace cmdline ----- /usr/bin/python -tt /usr/bin/repoquery --repofrompath=rawhide-rfa-20091018T224932Z,http://koji.fedoraproject.org/static-repos/dist-rawhide-current/x86_64/ --repoid=rawhide-rfa-20091018T224932Z --location bpg-nino-medium-cond-fonts-0:4.005-7.fc12.noarch component ----- python executable ----- /usr/bin/python kernel ----- 2.6.31.1-56.fc12.x86_64 package ----- python-2.6.2-2.fc12 reason ----- Process was terminated by signal 11
Created attachment 365202 [details] File: backtrace
Thanks for filing this report. It looks like Python is segfaulting whilst decoding the precompiled file: /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc from the disk representation back into its in-memory representation. What happens if you run each of the following commands: (a) rpm -Vf /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc (b) md5sum /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc (c) python -c "import urlgrabber.grabber" (d) can you attach the file to this bug please? Thanks
$rpm -Vf /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc $ $ md5sum /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc 4ca0a8698e4e5c2074654f10e0fb0fda /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc $ $ python -c "import urlgrabber.grabber" $
Created attachment 365277 [details] /usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc
Thanks for the info. I doublechecked the .pyc file you attached and it does appear to be valid. Please can you run the following fragment of code in the python interpreter, and let me know what happens: import marshal f = open('/usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc', 'rb') f.seek(8) co = marshal.load(f) # does it segfault here? print co Is the segfault reproducable, or was it a one-time only thing? I can't see an obvious problem looking at the exact crash site. Thanks. Notes to self: MAGIC for the file is 0xf2d1 = "Python 2.6a1: 62161 (WITH_CLEANUP optimization)"; type = 116 in frame 1 is TYPE_INTERNED ('t'), demarshalling a 16-byte string on 64-bit python.
(In reply to comment #5) > Please can you run the following fragment of code in the python interpreter, > and let me know what happens: > $ python Python 2.6.2 (r262:71600, Aug 21 2009, 12:23:57) [GCC 4.4.1 20090818 (Red Hat 4.4.1-6)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import marshal >>> f = open('/usr/lib/python2.6/site-packages/urlgrabber/grabber.pyc', 'rb') >>> f.seek(8) >>> co = marshal.load(f) >>> print co <code object <module> at 0x7f9a0ba63cd8, file "/usr/lib/python2.6/site-packages/urlgrabber/grabber.py", line 412> > Is the segfault reproducable, or was it a one-time only thing? The segfault has started happening regularly lately, but not every time python is called (I've also run a script that exercises this part a lot in the past days, I don't think I make such heavy use usually)
Thanks for the info. Can you think of any pattern that characterizes when the segfaults occur? Do the backtraces always look like the one you attached? (Looks like the component in bz got set to "0xFFFF"; I've set it back to "python"; I'm assuming this was an accident).
(In reply to comment #7) > Thanks for the info. Can you think of any pattern that characterizes when the > segfaults occur? It seems to happen on random times on random packages > Do the backtraces always look like the one you attached? Didn't look at them, if you want I'll push the next one via abrt (but I've finished proofing my script so I won't do that many repoquery calls now) If you want to replicate what I did, just run repo-font-audit from fontpackages-devel repeatedly against a yum repo that contains font packages > (Looks like the component in bz got set to "0xFFFF"; I've set it back to > "python"; I'm assuming this was an accident). This is probably an abrt bug
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.