All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Klaus Hochlehnert <1191606@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1191606] Re: qemu crashes with iscsi initiator (libiscsi) when	using virtio
Date: Tue, 18 Jun 2013 14:26:19 +0200	[thread overview]
Message-ID: <51C051EB.2030007@redhat.com> (raw)
In-Reply-To: <20130618093825.GC7649@stefanha-thinkpad.redhat.com>

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.

Cheers,
Laszlo

  reply	other threads:[~2013-06-18 12:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 23:48 [Qemu-devel] [Bug 1191606] [NEW] qemu crashes with iscsi initiator (libiscsi) when using virtio Klaus Hochlehnert
2013-06-16 23:54 ` [Qemu-devel] [Bug 1191606] " Klaus Hochlehnert
2013-06-17 13:02 ` [Qemu-devel] [Bug 1191606] [NEW] " Stefan Hajnoczi
2013-06-17 17:37 ` [Qemu-devel] [Bug 1191606] " Klaus Hochlehnert
2013-06-18  9:38   ` Stefan Hajnoczi
2013-06-18 12:26     ` Laszlo Ersek [this message]
2013-06-18 14:37       ` Stefan Hajnoczi
2013-06-18 18:01 ` Klaus Hochlehnert
2013-06-18 19:36   ` Laszlo Ersek
2013-06-19  4:34     ` ronnie sahlberg
2013-06-19  8:54       ` Stefan Hajnoczi
2013-06-19  9:17       ` Laszlo Ersek
2013-06-20 13:33         ` ronnie sahlberg
2013-06-20 14:47           ` Laszlo Ersek
2013-06-20 15:31             ` ronnie sahlberg
2013-06-20 15:47               ` Laszlo Ersek
2013-06-24 19:46 ` Laszlo Ersek (Red Hat)
2013-09-25  6:25 ` Klaus Hochlehnert
2013-09-25  7:30 ` Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51C051EB.2030007@redhat.com \
    --to=lersek@redhat.com \
    --cc=1191606@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.