Using libpurple in QuteCom (but with assertion fails)

[Ethan Blanton]

James Wald spake unto us the following wisdom:
> An assertion failure is an actual problem.  Getting the backtrace
> helps us to determine what execution path lead to an assertion
> failure.  An assert itself should never be a problem unless it is
> misused.

Unfortunately, there are a lot of spurious assertions in
libpurple/Pidgin.  We generally advise ignoring them unless there's a
specific reason to believe they're related to a problem.

I'd love to see that situation change, of course.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20080903/888f9090/attachment.sig>