You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is quite related to #820 , and also to #837
Using gcc 13.2.0, Ubuntu 24.04.
I would like to build a program with ASan, where the program needs to have some of its virtual memory map in fixed ranges. One of them starting at 0x2000_0000. It really does not matter why it needs to be fixed there, and at the end of the day, be this or any other reason where the elf ends up with a segment in the ASan fixed range, this issue would apply.
In any case, this leads to the error when trying to run ASan:
==..==Shadow memory range interleaves with an existing memory mapping. ASan cannot proceed correctly. ABORTING.
==..==ASan shadow was supposed to be located in the [0x1ffff000-0x3fffffff] range.
From the discussion in #837 I gather there has been thought on having ASan use a dynamic range instead of a fixed one, but it seems this track has not been pursued(?).
So my ask:
Is there any way today, to tell ASan, either at build time of the program, or at runtime either code at init, or thru an environment variable or.., to use a different address range?
Are you guys considering continuing in the track of having ASan use a dynamic range, instead of a fixed one?
This issue is quite related to #820 , and also to #837
Using gcc 13.2.0, Ubuntu 24.04.
I would like to build a program with ASan, where the program needs to have some of its virtual memory map in fixed ranges. One of them starting at 0x2000_0000. It really does not matter why it needs to be fixed there, and at the end of the day, be this or any other reason where the elf ends up with a segment in the ASan fixed range, this issue would apply.
In any case, this leads to the error when trying to run ASan:
From the discussion in #837 I gather there has been thought on having ASan use a dynamic range instead of a fixed one, but it seems this track has not been pursued(?).
So my ask:
CC @kcc
The text was updated successfully, but these errors were encountered: