mirror of
https://gitlab.gnome.org/GNOME/glib.git
synced 2025-02-23 18:52:09 +01:00
a5ae4f8f99
1998-12-09 Sebastian Wilhelmi <wilhelmi@ira.uka.de> * Made the thread related code follow GNU coding standard. * Made a comment (HOLDS:) above each function, that expects the given locks to be held. * Changed try_lock to trylock throughout. * glib.c: Eventually removed the #if 0'ed code for old GStaticMutex. * glib.c: Corrected g_trylock macro for G_DEBUG_LOCKS. * gmain.c (g_main_poll_add_unlocked): first take a new poll record form the poll_free_list. * gmem.c, gstrfuncs.c, gutils.c: Made it MT safe. * gthraed/*.c: Added copyright headers. * gthread/gthread-solaris.c: do not use g_log for errors, as g_log uses these module and endless recursions might happen, just use a plain fprintf(stderr,...). * gthread/gthread.c (g_thread_try_init): Call g_mutex_init(). * gthread/testgthread.c: updated test program.
General Information =================== This is GLib version 1.1.6. GLib, is a library which includes support routines for C such as lists, trees, hashes, memory allocation, and many other things. Versions of GLib prior to 1.1.0 are distributed with GTK+ versions prior to 1.1.0. The official ftp site is: ftp://ftp.gtk.org/pub/gtk The official web site is: http://www.gtk.org/ A mailing list is located at: gtk-list@redhat.com To subscribe: mail -s subscribe gtk-list-request@redhat.com < /dev/null (Send mail to gtk-list-request@redhat.com with the subject "subscribe") Installation ============ See the file 'INSTALL' How to report bugs ================== To report a bug, send mail either to gtk-list, as mentioned above, or to gtk-bugs@gtk.org. If you send mail to gtk-list, you must be subscribed yourself. In the mail include: * The version of GLib * Information about your system. For instance: - What operating system and version - What version of X - For Linux, what version of the C library And anything else you think is relevant. * How to reproduce the bug. If you can reproduce it with the testglib program that is built in the glib/ directory, that will be most convenient. Otherwise, please include a short test program that exhibits the behavior. As a last resort, you can also provide a pointer to a larger piece of software that can be downloaded. * If the bug was a crash, the exact text that was printed out when the crash occured. * Further information such as stack traces may be useful, but is not necessary. Patches ======= Patches can be uploaded to the incoming/ directory on ftp.gtk.org. Please follow the instructions there, and include your name and email address in the README file. If the patch fixes a bug, it is usually a good idea to include all the information described in "How to Report Bugs".