| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Consistency between const and non-const args for clone functions
|
| |
|
|
|
|
| |
they don't work with the current clang7 on Fedora29
|
| |
|
|
|
|
| |
hangs when iterating lots of invalid parameters (valid parameters already have a cap from f6c64896988644a7c6d4d5060f6ab574c2a62fbf) oss-fuzz issue 14809
|
|
|
|
|
|
|
|
|
|
| |
The libical's icalarray is not suitable for introspection much,
because it operates on bare structures, thus rather not allow
to add/get raw objects to/from it and let it be used for the timezone
arrays only.
The test itself could fail under libasan or a memory issue could
be reported when it had been run under valgrind.
|
|
|
|
|
|
| |
The function should pass the buffer length including
the nul-terminating character. Change also the 'encode' wrapper
similarly.
|
| |
|
| |
|
|
|
|
| |
in icalvalue_decode_ical_string(), with associated test
|
| |
|
|
|
|
| |
usage or hanging Alternate fix to #381.
|
|
|
|
|
|
| |
This provides a hard limit on parsing to prevent unbounded memory usage or hanging when expanding parameters or properties. RFC 5545 says lines should not exceed 75 octets, so this still provides a pretty large buffer for files to be non-conformant and still parse successfully. oss-fuzz issue 14180, 14171, and 14591."
This reverts commit 981f3dc6cdef0f140c048cb5de15c61a60a0cc6e.
|
|
|
|
| |
This reverts commit 81554e81f2422b6d7902c15d9deff49fb6fe787b.
|
|
|
|
| |
This reverts commit 562cce0fdc17fd68f2dd7711f2b737ecadf00892.
|
| |
|
|
|
|
| |
for strnlen()
|
|
|
|
| |
provides a hard limit on parsing to prevent unbounded memory usage or hanging when expanding parameters or properties. RFC 5545 says lines should not exceed 75 octets, so this still provides a pretty large buffer for files to be non-conformant and still parse successfully. oss-fuzz issue 14180, 14171, and 14591.
|
|
|
|
| |
Fixes memory leaks caused by the parser behaving incorrectly when the level is negative. oss-fuzz issue 14480, 14151, 14152, 14153, 14155.
|
| |
|
| |
|
|
|
|
| |
trusty is getting too old
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
when using BUILTIN_TZDATA (and encountering the location fallback)
|
|\ |
|
| |
| |
| |
| | |
i-cal-recurrence.xml
|
| |
| |
| |
| |
| |
| | |
itself
All the langbind methods are helpers for the bindings in libical, here the GObject Introspection already covers all the features.
|
| |
| |
| |
| |
| |
| |
| | |
Make sure that ICalFoo methods are prefixed i_cal_foo.
Always start method name with `new' when it is a creation method.
Clone method are not creation methods, remove the `new' prefix.
Remove _r suffix of methods returning ical strings as it is already clear.
|
| |
| |
| |
| | |
Add documentation to the delegate and provide the right annotations.
|
| |
| |
| |
| |
| |
| | |
This allows bindings to fully use the method with user_data.
i_cal_parser_string_line_generator is removed as it relies on internal structures.
i_cal_parser_set_gen_data is removed as it is directly called by the wrappers.
|
| |
| |
| |
| | |
Add array and array length annotations
|
| | |
|
|/
|
|
| |
Covers the things that the introspection fails to cover
|
|
|
|
| |
icalproperty_get_datetime_with_component
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Error: REVERSE_INULL:
src/libical-glib/i-cal-object.c:355: deref_ptr: Directly dereferencing pointer "iobject".
src/libical-glib/i-cal-object.c:365: check_after_deref: Null-checking "iobject" suggests that it may be null, but it has already been dereferenced on all paths leading to the check.
363|
364| if (is_global_memory) {
365|-> if (iobject) {
366| GlobalData *gd;
367|
------------------------------------------------------------------
Error: ALLOC_FREE_MISMATCH:
src/libical/vcomponent_cxx.cpp:922: alloc: Allocation of memory which must be freed using "operator delete".
src/libical/vcomponent_cxx.cpp:922: assign: Assigning: "related_param" = "trigger_prop->get_first_parameter(icalparameter_kind const(ICAL_RELATED_PARAMETER))".
src/libical/vcomponent_cxx.cpp:979: free: Calling "free" frees "related_param" using "free" but it should have been freed using "operator delete".
977|
978| if (related_param != NULL) {
979|-> free(related_param);
980| }
981|
------------------------------------------------------------------
Error: IDENTIFIER_TYPO:
libical-3.0.5/src/python/Component.py:796: identifier_typo: Using "properites" appears to be a typo:
* Identifier "properites" is only known to be referenced here, or in copies of this code.
* Identifier "properties" is referenced elsewhere at least 18 times.
src/python/Component.py:796: remediation: Should identifier "properites" be replaced by "properties"?
src/python/Component.py:138: identifier_use: Example 2: Using identifier "properties".
src/python/Component.py:674: identifier_use: Example 3: Using identifier "properties".
src/python/test.py:274: identifier_use: Example 4: Using identifier "properties" (9 total uses in this function).
src/python/test.py:393: identifier_use: Example 5: Using identifier "properties".
794| def duration(self, value=None):
795| if value != None:
796|-> due = self.properites('DUE')
797| for d in due:
798| self.remove_property(d) # Clear DUE properties
Signed-off-by: Allen Winter <allen.winter@kdab.com>
|
|
|
|
|
|
|
| |
The ICalTime functions which use ICalTimezone can have the zone
set to NULL, thus mark it as such in libical-glib as well.
Signed-off-by: Allen Winter <allen.winter@kdab.com>
|
| |
|
|
|
|
| |
the plan is for libical-glib to be stable in the 3.1 release
|
| |
|
|\ |
|
| | |
|
| |\
| | |
| | |
| | | |
https://github.com/tapkey/libical into tapkey-iterator-performance-next_year
|
| | | |
|