1
0
mirror of https://github.com/ioacademy-jikim/debugging synced 2025-06-22 15:26:30 +00:00
debugging/02_day/valgrind/valgrind-3.11.0/helgrind/tests/locked_vs_unlocked3.stderr.exp
2015-12-13 22:34:58 +09:00

35 lines
1.1 KiB
Plaintext

---Thread-Announcement------------------------------------------
Thread #x was created
...
by 0x........: pthread_create@* (hg_intercepts.c:...)
by 0x........: main (locked_vs_unlocked3.c:53)
---Thread-Announcement------------------------------------------
Thread #x was created
...
by 0x........: pthread_create@* (hg_intercepts.c:...)
by 0x........: main (locked_vs_unlocked3.c:54)
----------------------------------------------------------------
Lock at 0x........ was first observed
at 0x........: pthread_mutex_init (hg_intercepts.c:...)
by 0x........: main (locked_vs_unlocked3.c:51)
Address 0x........ is 0 bytes inside data symbol "mx"
Possible data race during write of size 4 at 0x........ by thread #x
Locks held: none
at 0x........: child_fn2 (locked_vs_unlocked3.c:38)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
This conflicts with a previous write of size 4 by thread #x
Locks held: 1, at address 0x........
at 0x........: child_fn1 (locked_vs_unlocked3.c:28)
by 0x........: mythread_wrapper (hg_intercepts.c:...)
...
Address 0x........ is 0 bytes inside data symbol "x"