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)
Fri, Nov 22, 3:35 PM
Unknown Object (File)
Oct 25 2024, 1:48 PM
Unknown Object (File)
Oct 14 2024, 4:27 AM
Unknown Object (File)
Oct 10 2024, 4:57 PM
Unknown Object (File)
Oct 10 2024, 9:01 AM
Unknown Object (File)
Oct 10 2024, 8:23 AM
Unknown Object (File)
Oct 10 2024, 4:16 AM
Unknown Object (File)
Sep 27 2024, 12:25 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