Mercurial > pidgin
annotate README.MTN @ 28866:419565a2ed9d
*** Plucked rev b0c392df480480c0a511e96fc7b2eb7f827e6efb (bcc0147bab874ca52c55ad4900545e17528bf8fd):
Save the event source ID for search_find_cb so that it's removed when the
log dialog is closed. This fixes a double free which might be caused by
having a large logset (and maybe pressing Close multiple times).
It looks something like this, with a few variations:
== Invalid read of size 8
== at 0x483001: search_find_cb (gtklog.c:425)
== by 0xBB91E50: g_main_context_dispatch (gmain.c:1824)
== by 0xBB953E7: g_main_context_iterate (gmain.c:2455)
== by 0xBB958BC: g_main_loop_run (gmain.c:2663)
== by 0x63AF606: gtk_main (gtkmain.c:1205)
== by 0x485ADF: main (gtkmain.c:978)
== Address 0x1b469860 is 56 bytes inside a block of size 72 free'd
== at 0x4C239EF: free (vg_replace_malloc.c:323)
== by 0x483A6C: destroy_cb (gtklog.c:223)
== by 0xAB9B12C: g_closure_invoke (gclosure.c:767)
== by 0xABB02B1: signal_emit_unlocked_R (gsignal.c:3247)
== by 0xABB1806: g_signal_emit_valist (gsignal.c:2980)
== by 0xABB1CD2: g_signal_emit (gsignal.c:3037)
== by 0xAB9B12C: g_closure_invoke (gclosure.c:767)
== by 0xABB02B1: signal_emit_unlocked_R (gsignal.c:3247)
== by 0xABB1806: g_signal_emit_valist (gsignal.c:2980)
== by 0xABB1CD2: g_signal_emit (gsignal.c:3037)
== by 0x630ECB4: gtk_real_button_released (gtkbutton.c:1707)
== by 0xAB9B12C: g_closure_invoke (gclosure.c:767)
==
Fixes #11071.
author | Daniel Atallah <daniel.atallah@gmail.com> |
---|---|
date | Thu, 07 Jan 2010 23:48:06 +0000 |
parents | e0bcb8cfda74 |
children |
rev | line source |
---|---|
16176
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
1 If you plan to use Pidgin, Finch and libpurple from our Monotone repository, |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
2 PLEASE read this message in its entirety! |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
3 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
4 Pidgin, Finch, and libpurple are a fast-moving project with a somewhat regular |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
5 release schedule. Due to the rate of development, the code in our Monotone |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
6 repository undergoes frequent bursts of massive changes, often leaving behind |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
7 brokenness and partial functionality while the responsible developers rewrite |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
8 some portion of code or seek to add new features. |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
9 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
10 What this all boils down to is that the code in our Monotone repository _WILL_ |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
11 sometimes be broken. Because of this, we ask that users who are not interested |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
12 in personally tracking down bugs and fixing them (without a lot of |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
13 assistance from the developers!) use only released versions. Since releases |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
14 will be made often, this should not prevent anyone from using the newest, |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
15 shiniest features -- but it will prevent users from having to deal with ugly |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
16 development bugs that we already know about but haven't gotten around to fixing. |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
17 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
18 If you are interested in hacking on Pidgin, Finch, and/or libpurple, please |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
19 check out the information available at: http://developer.pidgin.im |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
20 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
21 By far the best documentation, however, is the documented code. If you have |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
22 doxygen, you can run "make docs" in the toplevel directory to generate pretty |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
23 documentation. Otherwise (or even if you do!), the header files for each |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
24 subsystem contain documentation for the functions they contain. For instance, |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
25 conversation.h contains documentation for the entire purple_conversation_* |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
26 API, and account.h contains documentation for the purple_account_* API. |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
27 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
28 If you have questions, please feel free to contact the Pidgin, Finch, and |
23180
e0bcb8cfda74
Use "email" and "Email" consistently. This is potentially controversial,
Richard Laager <rlaager@wiktel.com>
parents:
16176
diff
changeset
|
29 libpurple developers by email at devel@pidgin.im or on IRC at irc.freenode.net |
16176
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
30 in #pidgin. Please do as much homework as you can before contacting us; the |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
31 more you know about your question, the faster and more effectively we can help! |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
32 |
83ec0b408926
Beat some older documentation into submission.
Richard Laager <rlaager@wiktel.com>
parents:
diff
changeset
|
33 Patches should be posted as Trac tickets at: http://developer.pidgin.im |