Summary: | FTBFS: g_warning misses a NULL second parameter. | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Diego Escalante Urrelo <diegoe> |
Component: | tp-farsight | Assignee: | Telepathy bugs list <telepathy-bugs> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | critical | ||
Priority: | medium | CC: | will |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Diego Escalante Urrelo
2009-03-10 22:52:33 UTC
Your proposed patch is wrong: g_warning is printf-like, and doesn't need a NULL terminator. What's the actual warning you're getting? The code is also wrong: it shouldn't be building a string and then passing it as the first argument to g_warning. The correct fix would be to change g_warning (msg); to g_warning ("%s", msg); I'm guessing that the problem is that the compiler is warning that a printf-style function is called with a non-literal as the first argument. These calls should be of the form: g_warning("%s", str); Diego, can you confirm? I dont' have a farsight src right now to check but I agree with you both. This appears to have been fixed, possibly in 0.0.7 by commit 6fae4cbe "Shut up compiler warning about unsecure printf strings". |
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.