[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ft-devel] Builtin way to trace freetype API calls?
|
From: |
Nikolay Sivov |
|
Subject: |
Re: [ft-devel] Builtin way to trace freetype API calls? |
|
Date: |
Mon, 6 Jun 2016 21:23:45 +0300 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 |
On 06.06.2016 21:08, Qian Hong wrote:
> Hi folks,
>
> I am working on Wine support for a closed source Win32 application.
> This Win32 application bundle a freetype library to process fonts:
>
> https://www.reasoncoresecurity.com/freetype.dll-0aa9e1bd9e67aa9852df16152a83fcb1e7886d48.aspx
>
> In order to understand how the application use freetype, I am hoping
> to tracing the freetype API calls. Is there something like `export
> FREETYPE_DEBUG=1` available so I can read freetype API logs?
>
> The freetype version is 2.4.3 according to resource dump from
> freetype.dll ( $ winedump -j resource freetype.dll )
>
> Thank you very much!
There's FT2_DEBUG envvar for that, documented in docs/DEBUG. This will
only work if
library was compiled with enabled tracing support.