https://bugs.kde.org/show_bug.cgi?id=410596
--- Comment #10 from Jiri Palecek <jpale...@web.de> --- (In reply to David Jarvie from comment #9) > Yes, there is a bug in removeKAEvents, and your patch looks good. I'll wait > for you to submit it in Phabricator. I've posted it. > The valgrind trace shows that a calendar added is being processed, and that > that is interrupted (while a 'new' is being executed) by the removal of a > calendar, and that in turn is interrupted (while a 'delete' is being > executed) by another removal of a calendar. I think this is a misunderstanding, the valgrind report for a wrong access contains three traces, one at the time of the access, second one at the time of the block being freed, third one at the time of its allocation. It isn't one backtrace of new interrupted while being executed. It would be very odd if that actually could happen. I admit it's not entirely legible here. I'll try to use attachments the next time, although it's tricky when you just copy output from terminal. -- You are receiving this mail because: You are watching all bug changes.
