[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init'
From: |
Werner LEMBERG |
Subject: |
Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init' |
Date: |
Sat, 25 Aug 2018 12:40:04 +0200 (CEST) |
>> Looks like a bug. Please provide a simple compilable example that
>> I can use for debugging.
>
> Sorry, sure, I forgot! You could use `2018-08-20-bitmaps' on my private
> fork like:
>
> $ git clone https://github.com/cherusker/freetype2-testing.git
> cherusker-freetype2-testing
> $ cd cherusker-freetype2-testing
> $ git checkout 2018-08-20-bitmaps
> $ cd fuzzing/scripts
> $ ./custom-script.sh
> ... <here go your settings, asan is required> ...
Following this recipe (using git 3763871e) it fails with
[100%] Linking CXX executable ../../bin/driver-asan-ubsan-o0-fttrace
../../lib/libfuzztargets.a(glyphvisitor-bitmap-handling.cpp.o):
In Funktion »GlyphVisitorBitmapHandling::blend(
FT_LibraryRec_*, FT_Bitmap_ const&, FT_Bitmap_&)«:
.../cherusker-freetype2-testing/fuzzing/src/visitors/glyphvisitor-bitmap-handling.cpp:136:
Warnung: undefinierter Verweis auf
»GlyphVisitorBitmapHandling::SOURCE_OFFSET«
.../cherusker-freetype2-testing/fuzzing/src/visitors/glyphvisitor-bitmap-handling.cpp:147:
Warnung: undefinierter Verweis auf
»GlyphVisitorBitmapHandling::COLOUR_PINK«
clang-6.0.1: error: linker command failed with exit code 1 (use -v to see
invocation)
src/driver/CMakeFiles/driver.dir/build.make:123: die Regel
für Ziel „bin/driver-asan-ubsan-o0-fttrace“ scheiterte
make[2]: *** [bin/driver-asan-ubsan-o0-fttrace] Fehler 1
CMakeFiles/Makefile2:161: die Regel
für Ziel „src/driver/CMakeFiles/driver.dir/all“ scheiterte
on my GNU/Linux box.
> Is that OK, or should I extract a teeny-tiny sample with just the 4
> to 5 necessary API calls?
The latter would be really nice, especially if written in C.
Werner
- [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/23
- Message not available
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Werner LEMBERG, 2018/08/24
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/24
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init',
Werner LEMBERG <=
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Werner LEMBERG, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Werner LEMBERG, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Werner LEMBERG, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', armin, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Alexei Podtelezhnikov, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Werner LEMBERG, 2018/08/25
- Re: [ft-devel] PCF: Issues with lazy copy in `ft_bitmap_glyph_init', Alexei Podtelezhnikov, 2018/08/25