what is the child process fork by init_libpurple in nullclient.c?

[sirtoozee]

Hi geek,

I noticed that there are some child process showing in my konsole like below:
root      4818  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4819  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4820  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4821  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4822  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4823  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4824  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4825  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4826  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4827  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4828  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4833  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4843  4811  0 19:46 pts/1    00:00:00 [libpurple] <defunct>
root      4854  4811  0 19:48 pts/1    00:00:00 [libpurple] <defunct>

when nullclient.c called the init_libpurple(), I just want to know
what, why and how created them.

And a guy, a pidgin fans in China.P.R, paid some attention to the
source code said it handled the DNS stuff. Really?

What`s more, the nullclient.c often show the ASSERT info just like
shown as below:
** (process:4811): CRITICAL **: x509_tls_peers_init: assertion `ret == 0' failed
How to fix it, thanks a lot ^_^

sirtoozee

-- 
An individual human existence should be like a river - small at first,
narrowly contained within its banks, and rushing passionately past
boulders and over waterfalls. Gradually the river grows wider, the
banks recede, the waters flow more quietly, and in the end, without
any visible break, they become merged in the sea, and painlessly lose
their individual being.