will explicit-address shmat() be supported?

[GoogleCodeExporter]

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.

Original issue reported on code.google.com by starligh...@gmail.com on 28 Oct 2014 at 5:35

[GoogleCodeExporter]

gcc 4.9.1

Original comment by starligh...@gmail.com on 28 Oct 2014 at 5:37

[GoogleCodeExporter]

Hi,
please move this issue to:
https://code.google.com/p/thread-sanitizer/issues/list
this project is about old valgrind-based tsan.

Original comment by dvyu...@google.com on 28 Oct 2014 at 8:39

[GoogleCodeExporter]

Done--sorry for the mistake.  I don't see how to delete the entry so please 
delete it or mark it resolved.

Original comment by starligh...@gmail.com on 28 Oct 2014 at 1:51