Issue 120 in data-race-test: will explicit-address shmat() be supported?
3 views
Skip to first unread message
data-ra...@googlecode.com
Oct 28, 2014, 1:35:27 AM10/28/14
to data-ra...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 120 by starligh...@gmail.com: will explicit-address shmat() be
supported?
https://code.google.com/p/data-race-test/issues/detail?id=120
After a successful try at running a large application with ASAN I made an
attempt at TSAN. TSAN throws a NULL dereference SEGV on the first access
to a shared memory segment mapped with an explicit address and I have the
distinct impression this case is either not supported or has not yet been
considered. Segments are successfully mapped in either the
0x6000_0000_0000 or 0x7000_0000_0000 ranges which are not (at least
initially) occupied by TSAN. With ASAN segment base addresses were biased
and successfully mapped in the 0x5000_0000_0000 range.
Can provide details and a concise test-case if a desire to pursue the issue
exists. If not please document the lack of support--have found found no
mention of it. Have long preferred explicit mapping addresses though the
conventional wisdom is to let the OS decide where to place them.
This app works with Valgrind and Helgrind, though here Valgrind core is
compiled such that it occupies 0x7_0000_0000 and the application's normal
preference for shamt() mappings is left unadjusted, occupying the range
0x3_0000_0000 to 0x6_FFFF_FFFF.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 120 by starligh...@gmail.com: will explicit-address shmat() be
supported?
https://code.google.com/p/data-race-test/issues/detail?id=120
After a successful try at running a large application with ASAN I made an
attempt at TSAN. TSAN throws a NULL dereference SEGV on the first access
to a shared memory segment mapped with an explicit address and I have the
distinct impression this case is either not supported or has not yet been
considered. Segments are successfully mapped in either the
0x6000_0000_0000 or 0x7000_0000_0000 ranges which are not (at least
initially) occupied by TSAN. With ASAN segment base addresses were biased
and successfully mapped in the 0x5000_0000_0000 range.
Can provide details and a concise test-case if a desire to pursue the issue
exists. If not please document the lack of support--have found found no
mention of it. Have long preferred explicit mapping addresses though the
conventional wisdom is to let the OS decide where to place them.
This app works with Valgrind and Helgrind, though here Valgrind core is
compiled such that it occupies 0x7_0000_0000 and the application's normal
preference for shamt() mappings is left unadjusted, occupying the range
0x3_0000_0000 to 0x6_FFFF_FFFF.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
data-ra...@googlecode.com
Oct 28, 2014, 1:37:27 AM10/28/14
to data-ra...@googlegroups.com
data-ra...@googlecode.com
Oct 28, 2014, 4:39:17 AM10/28/14
to data-ra...@googlegroups.com
Comment #2 on issue 120 by dvyu...@google.com: will explicit-address
Hi,
please move this issue to:
https://code.google.com/p/thread-sanitizer/issues/list
this project is about old valgrind-based tsan.
data-ra...@googlecode.com
Oct 28, 2014, 9:51:35 AM10/28/14
to data-ra...@googlegroups.com
Comment #3 on issue 120 by starligh...@gmail.com: will explicit-address
Done--sorry for the mistake. I don't see how to delete the entry so please
delete it or mark it resolved.
Reply all
Reply to author
Forward
0 new messages