Testing Environment =============================== Host: qemumips sato/sdk Kernel: Linux version 2.6.37.2-yocto-standard+ Image location: http://autobuilder.yoctoproject.org/nightly/20110305-4/machines/qemu/qemumips/ commit c192fefd868be53c20dfd8bc44e3e815cf53a10a Steps =============================== 1. Bootup target with sato/sdk image. 2. Type 'zypper search avahi' on target Observed Result =============================== 1. The first time when typing 'zypper search avahi', it has the 'Segmentation fault' error. When typing 'zypper search avahi' again, it has the '*** glibc detected *** zypper: corrupted double-linked list: 0x005d78b0 *** Aborted' error. 2. When typing 'zypper addrepo ...', it also has the '*** glibc detected *** zypper: munmap_chunk(): invalid pointer: 0x005d6090 *** Aborted' error. Please see below for more info. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ root@qemumips:~# zypper search avahi Loading repository data... Reading installed packages... S | Name | Summary | Type --+-------------------+-----------------------------------------------------------------------+-------- i | avahi | Avahi IPv4LL network address configuration daemon | package i | avahi-daemon | Avahi IPv4LL network address configuration daemon | package i | avahi-dev | Avahi IPv4LL network address configuration daemon - Development files | package i | libavahi-client3 | Avahi IPv4LL network address configuration daemon | package i | libavahi-common3 | Avahi IPv4LL network address configuration daemon | package i | libavahi-core7 | Avahi IPv4LL network address configuration daemon | package i | libavahi-glib1 | Avahi IPv4LL network address configuration daemon | package i | libavahi-gobject0 | Avahi IPv4LL network address configuration daemon | package Segmentation fault root@qemumips:~# zypper search avahi Loading repository data... Reading installed packages... S | Name | Summary | Type --+-------------------+-----------------------------------------------------------------------+-------- i | avahi | Avahi IPv4LL network address configuration daemon | package i | avahi-daemon | Avahi IPv4LL network address configuration daemon | package i | avahi-dev | Avahi IPv4LL network address configuration daemon - Development files | package i | libavahi-client3 | Avahi IPv4LL network address configuration daemon | package i | libavahi-common3 | Avahi IPv4LL network address configuration daemon | package i | libavahi-core7 | Avahi IPv4LL network address configuration daemon | package i | libavahi-glib1 | Avahi IPv4LL network address configuration daemon | package i | libavahi-gobject0 | Avahi IPv4LL network address configuration daemon | package *** glibc detected *** zypper: corrupted double-linked list: 0x005d78b0 *** Aborted root@qemumips:~# root@qemumips:~# zypper addrepo http://192.168.7.1/rpmrepo rpmrepo Adding repository 'rpmrepo' [done] Repository 'rpmrepo' successfully added Enabled: Yes Autorefresh: No URI: http://192.168.7.1/rpmrepo *** glibc detected *** zypper: munmap_chunk(): invalid pointer: 0x005d6090 *** Aborted root@qemumips:~#
Please verify this against the current nightly, this problem is maybe related to the fixes that went in for 721 and 722.
(In reply to comment #1) > Please verify this against the current nightly, this problem is maybe related > to the fixes that went in for 721 and 722. I think the bug should not be related to bug 721 and 722, becasue what Liang is using is the 20110305 image, which includes Qing's fixing. Liang, You can give more comments if I understand correct or not.
(In reply to comment #2) > (In reply to comment #1) > > Please verify this against the current nightly, this problem is maybe related > > to the fixes that went in for 721 and 722. > > I think the bug should not be related to bug 721 and 722, becasue what Liang is > using is the 20110305 image, which includes Qing's fixing. > > Liang, > You can give more comments if I understand correct or not. Yes, i have the same meaning with Jiajun. This probelm was found on 20110305 build, i am waiting for the nightly build to retry it, but this days nightly build does not have qemumips sato/sdk image build out. From Bug 721 Comment 11 from Qing, 'btw, zypper as current state does not support mips in its architecture table', maybe the fix for 721 and 722 does not apply for mips arch.
(In reply to comment #3) > From Bug 721 Comment 11 from Qing, 'btw, zypper as current state does not > support mips in its architecture table', maybe the fix for 721 and 722 does not > apply for mips arch. Non-support for mips causes bug 845 actually, not sure for this bug. However, it shouldn't crash at least. The crash root cause for x86_64 is now clearly identification, this seems a separate issue that may or may not be related to zypper's lacking of mips support
There is not have segfault when do 'zypper search xxx' on qemumips on current nightly build(20110313-2). Image location: http://autobuilder.yoctoproject.org/nightly/20110313-2/machines/qemu/qemumips/ commit a33a2cc024f9c9147c92c5da70d8fbb631b968f9
This issue is resolved on current nightly build (20110313-2). Image location: http://autobuilder.yoctoproject.org/nightly/20110313-2/machines/qemu/qemumips/ commit a33a2cc024f9c9147c92c5da70d8fbb631b968f9
Verify this bug on nightly build (20110313-2), and it is not occur. Image location: http://autobuilder.yoctoproject.org/nightly/20110313-2/machines/qemu/qemumips/ commit a33a2cc024f9c9147c92c5da70d8fbb631b968f9