rr, threads, and signal handlers

Wade Hennessey wadehennessey at gmail.com
Tue Nov 3 04:17:22 UTC 2015

I'm not doing anything to thread priorities.  -wade

On Mon, Nov 2, 2015 at 8:04 PM, Robert O'Callahan <robert at ocallahan.org>

> On Tue, Nov 3, 2015 at 5:02 PM, Robert O'Callahan <robert at ocallahan.org>
> wrote:
>> rr should allow a context switch in that case. I'm not sure why you're
>> deadlocking.
>> Inserting a sched_yield while busy-waiting should make the problem go
>> away. Does it?
>> Does the problem show up if you write a small standalone testcase with
>> the behavior you described?
> And, I assume you're not messing with thread priorities? If thread 2 had
> higher priority than thread 1 (e.g. via sched_setparam) I would expect that
> behavior.
> Rob
> --
> lbir ye,ea yer.tnietoehr  rdn rdsme,anea lurpr  edna e hnysnenh hhe uresyf
> toD
> selthor  stor  edna  siewaoeodm  or v sstvr  esBa  kbvted,t
> rdsme,aoreseoouoto
> o l euetiuruewFa  kbn e hnystoivateweh uresyf tulsa rehr  rdm  or rnea
> lurpr
> .a war hsrer holsa rodvted,t  nenh hneireseoouot.tniesiewaoeivatewt sstvr
> esn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/rr-dev/attachments/20151102/41d0dfa5/attachment-0001.html>

More information about the rr-dev mailing list