zig/mach
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

freetype: Avoid dereferencing null bitmap buffer.

Browse source 
For some characters (eg \r) the returned glyph will have .{.rows = 0, .width=0, .pitch = 0, .buffer = null}. In zig null[0..0] causes a panic rather than returning an empty slice.
This commit is contained in:
Jamie Brandon 2022-06-08 12:59:41 -07:00 • committed by Stephen Gutekanst
parent 86053d9969
commit 15c71f5135
2 changed files with 8 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
freetype/examples/single-glyph.zig
View file

@ -21,7 +21,7 @@ pub fn main() !void {
while (i < bitmap.rows()) : (i += 1) {
var j: usize = 0;
while (j < bitmap.width()) : (j += 1) {
const char: u8 = switch (bitmap.buffer()[i * bitmap.width() + j]) {
const char: u8 = switch (bitmap.buffer().?[i * bitmap.width() + j]) {
0 => ' ',
1...128 => ';',
else => '#',

9
freetype/src/freetype/image.zig
View file

@ -45,8 +45,13 @@ pub const Bitmap = struct {
return @intToEnum(PixelMode, self.handle.pixel_mode);
}
pub fn buffer(self: Bitmap) []const u8 {
pub fn buffer(self: Bitmap) ?[]const u8 {
const buffer_size = std.math.absCast(self.pitch()) * self.rows();
return self.handle.buffer[0..buffer_size];
return if (self.handle.buffer == null)
// freetype returns a null pointer for zero-length allocations
// https://github.com/hexops/freetype/blob/bbd80a52b7b749140ec87d24b6c767c5063be356/freetype/src/base/ftutil.c#L135
null
else
self.handle.buffer[0..buffer_size];
}
};