| Summary: | Protect concurrent access to XIM | ||
|---|---|---|---|
| Product: | xorg | Reporter: | Carlo Marchiori <carlo.marchiori> |
| Component: | Lib/Xlib | Assignee: | Xorg Project Team <xorg-team> |
| Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | 7.7 (2012.06) | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Carlo Marchiori
2013-09-08 08:06:51 UTC
As a clarification, I first posted a bug to uim, but they said it's not a bug of theirs. Muneyuki Noguchi changed bug 68885 What Removed Added Status NEW RESOLVED Resolution --- NOTOURBUG Comment # 1 on bug 68885 from Muneyuki Noguchi This bug has nothing to do with uim, which isn't a part of libX11. In this kind of situation, either the callee protects its global variabls or the caller does it in its stead. I'm not an expert C programmer so I don't know which is the usual practise (I understand that the absense of locks in the callee makes it generally more performant, but making the odds of crashes more likely if the caller is not aware of it). -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/31. |
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.