qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Paul Brook <paul@nowt.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [4693] Implement thread creation.
Date: Sun, 8 Jun 2008 23:34:26 +0300	[thread overview]
Message-ID: <20080608203423.GA28437@localhost.localdomain> (raw)
In-Reply-To: <E1K56e1-0001s7-H6@cvs.savannah.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]

On Sat, Jun 07, 2008 at 10:12:17PM +0000, Paul Brook wrote:
> Revision: 4693
>           http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4693
> Author:   pbrook
> Date:     2008-06-07 22:12:17 +0000 (Sat, 07 Jun 2008)
> 
> Log Message:
> -----------
> Implement thread creation.

Thanks for changes.

But I still have race condition somewhere:

[builder@localhost ~]$ cat test.c
int main()
{
        return 0;
}
[builder@localhost ~]$ gcc test.c
qemu: unhandled CPU exception 0x2 - aborting
R00=000009bd R01=00000085 R02=000000b1 R03=0006bbad
R04=41116554 R05=00000000 R06=4123b670 R07=00000004
R08=7c95e5c0 R09=00000000 R10=4123afb0 R11=41217124
R12=00000000 R13=41217030 R14=411184d8 R15=411184e0
PSR=60000010 -ZC- A usr32
Aborted
[builder@localhost ~]$ gcc test.c
qemu: uncaught target signal 11 (Segmentation fault) - exiting
[builder@localhost ~]$ gcc test.c
Internal resource leak before 41046814
Segmentation fault
[builder@localhost ~]$ gcc test.c
/home/kas/git/qemu/tcg/tcg.c:1762: tcg fatal error
Aborted
[builder@localhost ~]$ gcc test.c
qemu: unhandled CPU exception 0x2 - aborting
R00=00000000 R01=436c225c R02=00000004 R03=00000067
R04=436c2298 R05=00000001 R06=00000000 R07=00000004
R08=7c95e5c0 R09=00000000 R10=416e3fb0 R11=411ec124
R12=00008bf1 R13=411ec030 R14=416cf8ec R15=436e198c
PSR=60000010 -ZC- A usr32
Aborted
[builder@localhost ~]$ gcc test.c
qemu: uncaught target signal 11 (Segmentation fault) - exiting
[builder@localhost ~]$ gcc test.c
Internal resource leak before 409e3814
Segmentation fault
[builder@localhost ~]$ gcc test.c
qemu: unhandled CPU exception 0x2 - aborting
R00=000009bd R01=436e9453 R02=000000b1 R03=0006bbad
R04=43755554 R05=00000000 R06=41775670 R07=00000004
R08=7c95e5c0 R09=00000000 R10=41774fb0 R11=41751124
R12=00000000 R13=41751030 R14=437574d8 R15=437574e0
PSR=60000010 -ZC- A usr32
qemu: uncaught target signal 11 (Segmentation fault) - exiting

I cannot reproduce it with QEMU_STRACE=1, but I guess that this bug is
related to vfork();

-- 
Regards,  Kirill A. Shutemov
 + Belarus, Minsk
 + ALT Linux Team, http://www.altlinux.com/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-06-08 20:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 22:12 [Qemu-devel] [4693] Implement thread creation Paul Brook
2008-06-08 20:34 ` Kirill A. Shutemov [this message]
2008-06-09 11:53   ` Felipe Contreras
2008-06-09 12:12     ` Kirill A. Shutemov
2008-06-09 12:38       ` Laurent Desnogues
2008-06-09 12:40         ` Laurent Desnogues

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=20080608203423.GA28437@localhost.localdomain \
    --to=kirill@shutemov.name \
    --cc=paul@nowt.org \
    --cc=qemu-devel@nongnu.org \
    /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 NNTP newsgroup(s).