Bug 8040 - table caprtl_to_unicode not initialised to 0 in enter_cap_rtl
Summary: table caprtl_to_unicode not initialised to 0 in enter_cap_rtl
Status: NEW
Alias: None
Product: FriBidi
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Behdad Esfahbod
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-08-28 04:50 UTC by Moshe Kamensky
Modified: 2013-03-15 20:51 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
patch that fixes the described problem (594 bytes, patch)
2006-08-28 04:52 UTC, Moshe Kamensky
Details | Splinter Review

Description Moshe Kamensky 2006-08-28 04:50:54 UTC
When the caprtl_to_unicode table is initialised in
fribidi_char_set_enter_cap_rtl, the entries are not set to 0 after allocation,
but a few lines later this is checked as a condition for initialisation. As a
result, the table is not created properly, and fribidi_cap_rtl_to_unicode
doesn't work properly.

This is in version 0.10.7 of libfribidi
Comment 1 Moshe Kamensky 2006-08-28 04:52:21 UTC
Created attachment 6728 [details] [review]
patch that fixes the described problem
Comment 2 chemtech 2013-03-15 14:17:41 UTC
Moshe Kamensky 
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 3 Moshe Kamensky 2013-03-15 14:40:08 UTC
(In reply to comment #2)
> Moshe Kamensky 
> Do you still experience this issue with newer drivers ?
> Please check the status of your issue.

I don't know what is meant by "newer drivers". With the changes in the library I think this became irrelevant, but I didn't actually check that the bug disappeared.
Comment 4 Behdad Esfahbod 2013-03-15 20:51:15 UTC
(In reply to comment #2)
> Moshe Kamensky 
> Do you still experience this issue with newer drivers ?
> Please check the status of your issue.

Please stop leaving canned comments on every bug!  You are NOT helping.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.