[freetype2] anuj-distance-field fdf4191: [sdf] Added memory tracker.

Hello Werner, How is this: https://lists.nongnu.org/archive/html/freetype-commit/2020-07/msg00067.html ? Sent from Mail for Windows 10 

Re: Logging Library-GSOC

> I have added an option in `FT2_DEBUG` environment variable to > enable/disable the printing of FT_COMPONENT and Timestamp with a log > message. Looks good, thanks. > After looking at builds/windows/vc2010, builds/windows/visualc and > builds/windows/visualce I can see that they all depend on

Re: Logging Library-GSOC

> I was trying profiling on the example program given @ here > . I > have used the profiling tool inbuilt in Visual Studios but was > unable to extract useful information from it, therefore I have tried > a solution provided on Stack

Re: Logging Library-GSOC

Hi, I was trying profiling on the example program given @ here . I have used the profiling tool inbuilt in Visual Studios but was unable to extract useful information from it, therefore I have tried a solution provided on Stack Overflow

Re: Logging Library-GSOC

>> *Have you set `FT2_DEBUG=any:7` in the environment?* > > Sorry, I forgot to mention this, I have used FT2_DEBUG=any:7 with > OpenSans-Bold.ttf font. OK. > Also, I wanted to ask is this the right approach for profiling? I'm not an expert, sorry. However, you might also try `valgrind

Re: Logging Library-GSOC

On Thu, Jul 16, 2020 at 8:30 AM Priyesh kumar wrote: > > Hi, > I was trying profiling on the example program given @ here. > I have used the profiling tool inbuilt in Visual Studios but was unable to > extract useful information from it, therefore I have tried a solution provided > on Stack

Re: Logging Library-GSOC

> *Have you set `FT2_DEBUG=any:7` in the environment?* Sorry, I forgot to mention this, I have used FT2_DEBUG=any:7 with OpenSans-Bold.ttf font. *> You should also use a> well-hinted TrueType font like 'Arial' to get a large bunch of> instruction debugging.* Thanks, I will use this font.

Re: Logging Library-GSOC

On Thu, Jul 16, 2020 at 9:51 AM Werner LEMBERG wrote: > > > >> *Have you set `FT2_DEBUG=any:7` in the environment?* > > > > Sorry, I forgot to mention this, I have used FT2_DEBUG=any:7 with > > OpenSans-Bold.ttf font. > > OK. > > > Also, I wanted to ask is this the right approach for profiling? >

Re: [Freetype-devel] Re: GSOC - Distance Fields

> On Jul 16, 2020, at 00:42, Werner LEMBERG wrote: > > >>> I would be less worried about FT_Property_Set if FreeType reserved >>> the right to remove (ignore) or change properties when it is >>> reasonable to do so, i.e. properties should not be considered a >>> part of API. >> >> Does

Re: Logging Library-GSOC

Hi Vincent, Thanks for the suggestion it seems very helpful, I will try it and let you know in case of any query. Thanks, Priyesh On Thu, Jul 16, 2020 at 4:14 PM Vincent Torri wrote: > On Thu, Jul 16, 2020 at 9:51 AM Werner LEMBERG wrote: > > > > > > >> *Have you set `FT2_DEBUG=any:7` in the

Re: [freetype2] anuj-distance-field d97e060: [sdf] Added total memory allocation log.

> What exactly do you mean with 'memory debug > table'? I was thinking about the debug table that is used internally in freetype i.e. 'FT_MemTableRec'. But it is internal to 'ftdbgmem.c' I tried a lot to use some structure to track the allocations, but it requires a significant amount of changes