Poisoning in HotSpot
Kim Barrett
kim.barrett at oracle.com
Wed Dec 4 12:42:15 UTC 2024
On 12/1/24 7:09 PM, David Holmes wrote:
> On 2/12/2024 2:13 am, Kim Barrett wrote:
>> Unfortunately, there's a potentially fatal problem with this whole
>> approach.
>> We don't have a mechanism for turning it off over some context. We
>> need this
>> because there are files that ere not ours that are subject to our
>> headers.
>> Consider gtest, for example. Apparently there are *lots* of calls to
>> sprintf,
>> for example.
>>
>> I've not yet come up with a way for this new mechanism to deal with
>> that.
>
> Somewhat crude but couldn't gtests #define USING_GTEST before
> including our headers and then we could make the forbidden stuff
> conditional on ifndef USING_GTEST. ??
Things are more complicated than that, unfortunately.
I think I might have a way forward, in part using that kind of thing.
But it might interfere with other future work.
More information about the hotspot-dev
mailing list