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

Authored by dfaure on Jul 31 2017, 4:55 PM.

Tags

Referenced Files

	F11884971: D497.diff
	Wed, Apr 24, 3:28 PM

	Unknown Object (File)
	Tue, Apr 23, 1:30 AM

	Unknown Object (File)
	Thu, Apr 18, 1:02 PM

	Unknown Object (File)
	Wed, Apr 17, 7:13 PM

	Unknown Object (File)
	Wed, Apr 17, 2:00 AM

	Unknown Object (File)
	Sun, Apr 7, 2:48 PM

	Unknown Object (File)
	Mar 16 2024, 3:59 PM

	Unknown Object (File)
	Mar 11 2024, 12:21 PM

View All 60 Files

Subscribers

None

Details

Reviewers

mollekopf
• knauss
knauss2

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

dfaure created this revision.Jul 31 2017, 4:55 PM

dfaure added reviewers: mollekopf, • knauss, knauss2.Jul 31 2017, 4:57 PM

dfaure added a project: KDE PIM Developers.

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

Revision Contents
Changeset List

Path

Size

kolabformat/

v2helpers.h

2 lines

Diff 1151

View Options

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