From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46535) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UoxB2-00043J-0r for qemu-devel@nongnu.org; Tue, 18 Jun 2013 10:46:37 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Uox2a-00019C-FH for qemu-devel@nongnu.org; Tue, 18 Jun 2013 10:37:51 -0400 Received: from mail-wi0-x22d.google.com ([2a00:1450:400c:c05::22d]:36332) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Uox2a-00018e-7f for qemu-devel@nongnu.org; Tue, 18 Jun 2013 10:37:48 -0400 Received: by mail-wi0-f173.google.com with SMTP id hq4so3515096wib.0 for ; Tue, 18 Jun 2013 07:37:47 -0700 (PDT) Date: Tue, 18 Jun 2013 16:37:44 +0200 From: Stefan Hajnoczi Message-ID: <20130618143744.GQ7649@stefanha-thinkpad.redhat.com> References: <20130616234827.23764.98763.malonedeb@wampee.canonical.com> <20130617173757.22199.53209.malone@gac.canonical.com> <20130618093825.GC7649@stefanha-thinkpad.redhat.com> <51C051EB.2030007@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51C051EB.2030007@redhat.com> Subject: Re: [Qemu-devel] [Bug 1191606] Re: qemu crashes with iscsi initiator (libiscsi) when using virtio List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Klaus Hochlehnert <1191606@bugs.launchpad.net>, qemu-devel@nongnu.org On Tue, Jun 18, 2013 at 02:26:19PM +0200, Laszlo Ersek wrote: > On 06/18/13 11:38, Stefan Hajnoczi wrote: > > On Mon, Jun 17, 2013 at 05:37:57PM -0000, Klaus Hochlehnert wrote: > >> Without debug information I just can provide this (on that server I > >> can't recompile qemu with debugging information): > >> > >> warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffe67fe000 > >> 0x00007f1bca857313 in poll () from /lib/x86_64-linux-gnu/libc.so.6 > >> (gdb) c > >> Continuing. > >> [New Thread 0x7f1bb9a64700 (LWP 36180)] > >> [Thread 0x7f1bb9a64700 (LWP 36180) exited] > >> [New Thread 0x7f1bb9a64700 (LWP 36181)] > >> [Thread 0x7f1bb9a64700 (LWP 36181) exited] > >> [New Thread 0x7f1bb9a64700 (LWP 36207)] > >> > >> Program received signal SIGABRT, Aborted. > >> 0x00007f1bca7a5425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 > > > > The program invoked abort(3). This is a deliberate fatal error case. > > > > If you're using distro packages, please do the backtrace without symbols > > ("bt" and "info proc mappings") when gdb stops with SIGABRT and post the > > package version and distro you are using. > > > > Then I'll download the debuginfo packages from the distro and look up > > the symbols manually. > > > > If you're using a QEMU built from source then I would need the symbols > > from you. > > Yes. Yesterday I started responding to this report along the same lines > -- SIGABRT + raise() is assert() or abort(), but there was no error > message, hence abort(). > > Also, the reporter said in the opening comment that he used > > Host OS: Ubuntu 12.04 with 13.04-Kernel (3.8) > > which does ship a debuginfo package for qemu-kvm ("qemu-kvm-dbgsym"), > just some extra repos are needed: > > https://wiki.ubuntu.com/DebuggingProgramCrash#Debug_Symbol_Packages > > Thus I wanted to recommend the reporter to install the debuginfo package > and reproduce the crash (as this would not require him to rebuild anything). > > And that's when I noticed > > qemu version 1.5.0 > > (which is not Ubuntu's pristine version in the 12.04 release, ie. it's > probably a manual build), *with* > > on that server I can't recompile qemu with debugging information > > and decided it was a lost cause and deleted my email. I don't think it's a lost cause, we can figure it out but effort will be required on all sides. Stefan