Summary: | Impossible to unwind error while creating array of structs without assert() or memory leak | ||
---|---|---|---|
Product: | dbus | Reporter: | Scott James Remnant <scott> |
Component: | core | Assignee: | Havoc Pennington <hp> |
Status: | RESOLVED FIXED | QA Contact: | John (J5) Palmieri <johnp> |
Severity: | major | ||
Priority: | medium | CC: | mbiebl, walters |
Version: | 1.2.x | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Suggested patch
Patch Patch to make dbus_message_append_args_valist() abandon the array container adds an asserting test case |
Description
Scott James Remnant
2009-06-16 08:33:40 UTC
Created attachment 26854 [details] [review] Suggested patch One thing to figure out here is why the current memory leak/OOM tests aren't hitting this. Should we also fix say dbus_message_append_args_valist to use this function? I'd like to see a test case with the patch, probably in dbus-marshal-recursive-util.c. Created attachment 26855 [details] [review] Patch Slight think-o in the previous patch - updated I suspect the current OOM tests don't hit this precisely because dbus_message_append_args_valist doesn't use it? I can't see any tests for dbus_message_iter_open_container() Created attachment 26859 [details] [review] Patch to make dbus_message_append_args_valist() abandon the array container Created attachment 27528 [details] [review] adds an asserting test case Here's a test case that'll cause the assert (rather than the leak) to fix, we replace _close_container with the new _abandon_container functions Looks good then, thanks! committed and pushed |
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.