public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patatetom at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/10051] New: segfault with libc and qemu when socket listen used
Date: Thu, 09 Apr 2009 20:15:00 -0000	[thread overview]
Message-ID: <20090409201530.10051.patatetom@gmail.com> (raw)

Hi,

On Arch Linux...

Description:

Starting qemu or kvm with "-net socket,listen=:1234" option crash with
segmentation fault.
In /var/log/everything.log : "kernel: qemu[5852]: segfault at 0 ip b7bf8063 sp
bfee197c error 4 in libc-2.9.so[b7b85000+140000]"

Additional info:
* package version(s)
* config and/or log files etc.

qemu | grep version
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard

pacman -Qs | grep glibc
local/glibc 2.9-4 (base)

Steps to reproduce:

qemu -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net socket,listen=:12345
or
qemu -enable-kvm -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net
socket,listen=:12345


The bug is already reported in bug section on Arch Linux home.

-- 
           Summary: segfault with libc and qemu when socket listen used
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: patatetom at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: 2.9-4
  GCC host triplet: 2.6.29


http://sourceware.org/bugzilla/show_bug.cgi?id=10051

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


             reply	other threads:[~2009-04-09 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09 20:15 patatetom at gmail dot com [this message]
2009-04-10 19:40 ` [Bug libc/10051] " patatetom at gmail dot com
2010-06-01  4:07 ` pasky at suse dot cz

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=20090409201530.10051.patatetom@gmail.com \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).