Page MenuHomePhorge

Well, no, don't abort when encountering invalid XML.
AbandonedPublic

Authored by dfaure on Jul 31 2017, 4:55 PM.
Referenced Files
Unknown Object (File)
Tue, Feb 11, 3:42 AM
Unknown Object (File)
Tue, Feb 11, 1:05 AM
Unknown Object (File)
Tue, Feb 11, 1:05 AM
Unknown Object (File)
Sun, Feb 2, 4:56 AM
Unknown Object (File)
Wed, Jan 29, 3:22 PM
Unknown Object (File)
Tue, Jan 28, 9:12 PM
Unknown Object (File)
Tue, Jan 28, 1:15 PM
Unknown Object (File)
Mon, Jan 27, 1:10 PM
Subscribers
None

Details

Summary

With kolab shared folders, you always risk getting some crap as input,
and an abort is just too much.

Diff Detail

Repository
rLK libkolab
Branch
libkolab-1.0
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 11471
Build 9233: arc lint + arc unit

Event Timeline

I was wrong, Critical doesn't abort. What happens is a crash on null pointer just after this method returns KCalPtr(). Here's the proper fix: https://git.kolab.org/D503