-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NaN values in vectoriser #15
Comments
Can you give an example which characters from which fonts, and which FTGL drawing mode and settings you used to cause the problem, so I can reproduce it? Note that my fork (https://github.com/frankheckenbach/ftgl) seems to be the "official" one now (e.g. used in Debian). ulrichard didn't want to keep maintaining this one anymore. |
Sure thing! You'll have it on tuesday next week.
…On Thu, 11 Jul 2019, 23:59 frankheckenbach, ***@***.***> wrote:
Can you give an example which characters from which fonts, and which FTGL
drawing mode and settings you used to cause the problem, so I can reproduce
it?
Note that my fork (https://github.com/frankheckenbach/ftgl) seems to be
the "official" one now (e.g. used in Debian). ulrichard didn't want to keep
maintaining this one anymore.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15?email_source=notifications&email_token=AAH2DZ6DVS3T33KR4HJ4I6DP66UNHA5CNFSM4IBC3KFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZYDJYY#issuecomment-510670051>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAH2DZYQBJJFK5KRFKMR4MTP66UNHANCNFSM4IBC3KFA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This here crashes when d[0] or d[1] is NaN which apparently can happen with some characters in some fonts. Not sure why there would be such values.
ftgl/src/FTVectoriser.cpp
Line 321 in 16f7667
This is where the segfault happens (inside the glu library):
ftgl/src/FTVectoriser.cpp
Line 326 in 16f7667
I have implemented a crude fix here:
vovoid@d7b50a5
The text was updated successfully, but these errors were encountered: