From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: palves@redhat.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Crash on thread id wrap around
Date: Thu, 26 Mar 2015 13:05:00 -0000 [thread overview]
Message-ID: <201503261305.t2QD5A9h030233@glazunov.sibelius.xs4all.nl> (raw)
In-Reply-To: <1427373950-30952-1-git-send-email-palves@redhat.com> (message from Pedro Alves on Thu, 26 Mar 2015 12:45:50 +0000)
> From: Pedro Alves <palves@redhat.com>
> Date: Thu, 26 Mar 2015 12:45:50 +0000
>
> I managed to come up with a test that reliably reproduces this. It
> relies on pids wrapping around though, so could potentially take a
> while. On my box that's 4 seconds; on gcc110, a PPC box which has
> max_pid set to 65536, it's over 10 seconds. So I made the test
> compute how long that would take, and cap the time waited if that
> would be too long.
You can't really count on thread IDs wrapping on systems that
randomize them. There is still a chance that you'll reuse on of
course. Not much you can do about this, but folks should be aware
that this may cause non-reproducable test results on some systems.
next prev parent reply other threads:[~2015-03-26 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 12:45 Pedro Alves
2015-03-26 13:05 ` Mark Kettenis [this message]
2015-04-01 12:48 ` [pushed] " Pedro Alves
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=201503261305.t2QD5A9h030233@glazunov.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=palves@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