Behdad Esfahbod
Behdad Esfahbod
Right. Having a --extents or something is useful regardless. We've had an issue about that.
I like to fix this, but the approach looks rather fragile to me.
This also affects harfRuzz.@dfrg
Oops. Thanks. Will check.
I assume compiling with -O0 the warning goes away? It would immensely help my debugging if I can see an non-inlined stacktrace.
Thanks. At this point I think I can proceed by some code reading. It looks like one of the objects we return Null for, is not necessarily bounded in size....
It's actually conceivable that we get that warning but it not actually being a bug. In a union for example. But I don't believe that's the cause here.
Fix the include issue. Thank you.
Fixed. Thanks.
Nothing actionable here unfortunately.