graphene-hardened-malloc: 190405.003.2019.04.01.19 -> 1 #65021
Conversation
|
Wherever the bug was, I wanted to make sure this library was having an effect, because this is exactly the sort of thing which would easily be able to fail silently and could be doing bugger all for years without anyone noticing. And that could be for any reason from mis-compilation to the wrapper shell script being installed stupidly. I'm not quite in a position to test this right this second, so I can't say much more about the failure right now... |
|
Ok - it works if you just add |
|
While you're at it, how about adding |
The initial stable standalone release. The integer numbered tags are the standalone releases, while the PQ3B.190705.003.2019.07.01.21 style tags are part of GrapheneOS releases. For us it probably makes the most sense to track the standalone releases.
joachifm
force-pushed
the
graphene-hardened-malloc
branch
from
c5c3559
to
948d2e3
Compare
|
@risicle thank you |
|
@GrahamcOfBorg build graphene-hardened-malloc |
|
@GrahamcOfBorg test hardened |
The initial stable standalone release.
The integer numbered tags are the standalone releases, while the
PQ3B.190705.003.2019.07.01.21 style tags are part of GrapheneOS releases.
For us it probably makes the most sense to track the standalone releases.
Note that the install check phase currently fails, so this is WIP. It's a little unclear to me that the install check phase is all that useful, does it really uncover problems in the packaging or upstream bugs? It seems to me primarily the latter. @risicle thoughts on this?