Summary: | Odd segmentation fault error on "Safely unmerging already-installed instance" line | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sophie Hamilton <gentoo-bugs> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | dev-portage |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge.log - everything since last successful unmerge.
out.log - output on stdout from failed emerge command err.log.bz2 - bzip'd output on stderr (includes strace) from failed emerge command |
Description
Sophie Hamilton
2005-08-10 12:20:00 UTC
An update on this: Forgetting what I said about not doing any more emerges until you said (sorry guys!) I did an "emerge -u world" after sync'ing, and I had the same problem on a different package, sys-apps/man-pages-2.02. This was the first package to be unmerged after museseq, so maybe it's some sort of problem with fluidsynth and/or the "fluidsynth" USE flag? If not, then I doubt that it's a problem with any particular packages, but rather with emerge, and furthermore, probably something on my system. Here are the last few lines of my /var/log/emerge.log file: ===== 1123968552: Started emerge on: Aug 13, 2005 22:29:12 1123968552: *** emerge --update world 1123968558: >>> emerge (1 of 7) sys-apps/man-pages-2.07 to / 1123968558: === (1 of 7) Cleaning (sys-apps/man-pages-2.07::/usr/portage/sys-apps/man-pages/man-pages-2.07.ebuild) 1123968560: === (1 of 7) Compiling/Merging (sys-apps/man-pages-2.07::/usr/portage/sys-apps/man-pages/man-pages-2.07.ebuild) 1123968689: === (1 of 7) Post-Build Cleaning (sys-apps/man-pages-2.07::/usr/portage/sys-apps/man-pages/man-pages-2.07.ebuild) 1123968693: >>> AUTOCLEAN: sys-apps/man-pages 1123968698: === Unmerging... (sys-apps/man-pages-2.02) ===== I should note here that this seems to be a generic thing about unmerging, because this time it was an update, not a re-emerge of the same version. The output this time is at http://matrix.theblob.org/man-pages.txt . Once more, a summary: ===== >>> /usr/share/man/man3p/cacoshl.3p.gz >>> /usr/share/man/man3p/sinl.3p.gz [...] >>> /usr/share/man/man3p/fseeko.3p.gz >>> /usr/share/man/man3p/memmove.3p.gz >>> Regenerating /etc/ld.so.cache... >>> sys-apps/man-pages-2.07 merged. sys-apps/man-pages selected: 2.02 protected: 2.07 omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... >>> Unmerging in: 5 4 3 2 1 >>> Unmerging sys-apps/man-pages-2.02... No package files given... Grabbing a set. Segmentation fault downstairs ciaran # ===== I'm at a bit of a loss here. I've bumped the severity up a level because it's causing me not to be able to unmerge packages, it seems, and files are left on the system. I'm attaching everything in my emerge.log file since my last successful unmerge. Unfortunately a lot of packages has been emerged, and of course the cause might not even be in there. But it's there if you need to look at it. More as I find things out. Created attachment 65966 [details]
emerge.log - everything since last successful unmerge.
Here's everything since my last successful unmerge. The unmerge command that
was successful is also included in this log, at the beginning. Notice that for
the unmerge of media-sound/museseq-0.6.2-r1 and sys-apps/man-pages-2.02 (having
been upgraded to sys-apps/man-pages-2.07), there is no "*** exiting
successfully" line, because the segfault occurred.
Well, hard to debug without knowing whate xactly segfaults. strace log would help. Dangit, this appears to be an intermittent problem. I looked for a package to unmerge, and chose esearch because it's both small and I have eix now anyway, which is a lot faster. I tried doing the command "strace -f emerge unmerge esearch 2>err.log | tee out.log", but the command completed okay, and the package was unmerged properly. So I re-emerged esearch, hoping to try some different things. The emerge completed fine, but then, unexpectedly (for me, anyway), it un-emerged sys-apps/man-pages-2.02; I'm guessing that it was noted in a file somewhere that that unemerge should take place, and emerge saw it hadn't been done yet. In any case, that unemerge completed successfully too. More info as I can come up with it. Okay, I think I just got another segfault. This time I did "strace -f emerge esearch 2>err.log | tee out.log" to re-emerge esearch on top of itself. I'll attach both files (well, I'll bzip2 err.log as it's 23MB) to this bug. Created attachment 65994 [details]
out.log - output on stdout from failed emerge command
Created attachment 65995 [details]
err.log.bz2 - bzip'd output on stderr (includes strace) from failed emerge command
Just a quick update. This is still happening, even after a reboot, and it still seems to be somewhat intermittent. Is there any more information I can give that might help? Another update; I used a rescue Portage archive to emerge the latest Portage again. A test update of another package seemed to work, so here's hoping. It was at this point that I realised I had forgotten to mention something that I really should have mentioned at the start, but I completely forgot about: I had actually modified the 'emerge' command as directed in http://forums.gentoo.org/viewtopic.php?t=153921 to use psyco to apparently speed things up. It is entirely possible that that's what caused it, although I didn't have problems at first. Nonetheless, I'll be testing it now with and without and will report back on whether psyco seems to be causing the problem. If that's indeed the problem, then I humbly apologise for wasting the Gentoo devs' time. :( Actually, looking at the forum thread, others have reported segfaults in exactly the same manner. I'm very embarrassed now. I'm truly sorry. This bug should probably be marked INVALID now. Interesting...but not a supported feature ;) Note, psyco doesn't really make emerge faster. In fact, my testing showed that the overhead of doing a full (rather than JIT) optimization actually made it slower. Yeah, I noticed that I wasn't really getting any speedup. I should have removed it knowing that, but I left it in and completely forgot about it. If I'd remembered I would have tried that first before submitting the bug. As I said in the tread, I won't be touching emerge again. :D |