On Wed, Mar 1, 2017 at 2:00 AM, Owen Waller <go-n...@kulawe.com> wrote: > Hi Dimitry, > > The make goal of the current mapping is to make MemToShadow function > fast (no memory accesses, no branching). > For starters you can take any simple mapping at the cost making > MemToShadow slower. > > > OK that's good. As I wasn't intending to do anything apart from put in the > new memory map, rebuild things and then try it against some sort of hello > world example. > > I do not want to be changing any code beyond this if a can avoid it. > > > and do you want > to take a stab at what the mappings might be for a 32 bit system? > > > I don't have time to work on this. > > > I understand that. But at the minute, I don't understand how the numbers in > the memory map are arrived at. Is the process documented somewhere so I can > work this out for myself?
The mapping needs to satisfy the following requirements: 1. For all user memory regions there are 4x shadow regions. 2. For all user memory regions there are 0.5x meta shadow regions. 3. There is a region for thread traces. 4. +maybe a region for internal heap. > You need clang as it contains the master copy of tsan runtime. Here > are some building instructions: > https://github.com/google/sanitizers/wiki/AddressSanitizerHowToBuild > > > Thank you for this. It looks like I'll need to set up clang etc first. > > Owen -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
