Bug ID: 394361
           Summary: [Enhancement] : Client request to control
                    thread-yielding in valgrind
           Product: valgrind
           Version: 3.14 SVN
          Platform: RedHat RPMs
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
  Target Milestone: ---

Created attachment 112702


I have created a valgrind client-request "VALGRIND_YIELD", which makes current
running thread in valgrind to yield. 
This helps in scenario where, app has multiple consumer threads and those
threads are processing executing grabbed-objects. And there is a possibility of
data-race between execution of 2 grabbed objects. But since helgrind by default
runs a thread for 100000 basic-blocks, a single consumer-thread tends to grab
all object and hence no race happens with helgrind.
But with this client-request, after client-specific number of grabbed objects a
consumer-thread can yield to other consumer-thread and we can re-produce
race-causing scenario with helgrind as well.

I have patch attached with bugz. Kindly review and patch it into valgrind.

Thanks & Regards
Manish Goel

You are receiving this mail because:
You are watching all bug changes.

Reply via email to