dbus ChangeLog,1.962,1.963
Robert McQueen
robot101 at freedesktop.org
Wed Feb 15 16:43:43 PST 2006
- Previous message: dbus/python _dbus.py, 1.15, 1.16 dbus_bindings.pyx, 1.20,
1.21 matchrules.py, 1.5, 1.6
- Next message: dbus/dbus dbus-message.c,1.174,1.175 dbus-string.c,1.68,1.69
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
Update of /cvs/dbus/dbus
In directory gabe:/tmp/cvs-serv3873
Modified Files:
ChangeLog
Log Message:
2006-02-16 Robert McQueen <robot101 at debian.org>
* dbus/dbus-message.c (dbus_message_iter_get_fixed_array):
Patch from Rob Taylor <rob.taylor at collabora.co.uk> to correct a bogus
assertion that the next element to read from the iter is fixed in
size. This is not the case when you are at the end of the iter,
because the next element type is INVALID.
* dbus/dbus-string.c (_dbus_string_init_const_len): Correct a
a bogus assert which means that you may not initialise a 0-length
string unless you provide a non-NULL pointer. This prevented
you from marshalling messages containing zero-length arrays in
some cases.
* glib/dbus-gvalue.c (demarshal_collection_array): Another patch
from Rob to correct bogus asserts when trying to demarshal an
array and get_fixed_array got you 0 elements. Append nothing to
the GArray in this case.
* test/glib/test-dbus-glib.c: Add a test case for round-tripping
an empty array via the glib bindings. Without all of the above
patches, this new test fails.
Index: ChangeLog
===================================================================
RCS file: /cvs/dbus/dbus/ChangeLog,v
retrieving revision 1.962
retrieving revision 1.963
diff -u -d -r1.962 -r1.963
--- ChangeLog 15 Feb 2006 23:45:48 -0000 1.962
+++ ChangeLog 16 Feb 2006 00:43:41 -0000 1.963
@@ -1,5 +1,28 @@
2006-02-16 Robert McQueen <robot101 at debian.org>
+ * dbus/dbus-message.c (dbus_message_iter_get_fixed_array):
+ Patch from Rob Taylor <rob.taylor at collabora.co.uk> to correct a bogus
+ assertion that the next element to read from the iter is fixed in
+ size. This is not the case when you are at the end of the iter,
+ because the next element type is INVALID.
+
+ * dbus/dbus-string.c (_dbus_string_init_const_len): Correct a
+ a bogus assert which means that you may not initialise a 0-length
+ string unless you provide a non-NULL pointer. This prevented
+ you from marshalling messages containing zero-length arrays in
+ some cases.
+
+ * glib/dbus-gvalue.c (demarshal_collection_array): Another patch
+ from Rob to correct bogus asserts when trying to demarshal an
+ array and get_fixed_array got you 0 elements. Append nothing to
+ the GArray in this case.
+
+ * test/glib/test-dbus-glib.c: Add a test case for round-tripping
+ an empty array via the glib bindings. Without all of the above
+ patches, this new test fails.
+
+2006-02-16 Robert McQueen <robot101 at debian.org>
+
* glib/dbus-gmain.c: Make the previous commit compile.
* python/_dbus.py, python/matchrules.py: Patch from Ole Andre
- Previous message: dbus/python _dbus.py, 1.15, 1.16 dbus_bindings.pyx, 1.20,
1.21 matchrules.py, 1.5, 1.6
- Next message: dbus/dbus dbus-message.c,1.174,1.175 dbus-string.c,1.68,1.69
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the dbus-commit
mailing list