The main purpose of a bug report is to enable us to fix the bug. The most important prerequisite for this is that the report must be complete and self-contained, which we explain in detail below.
Before you report a bug, please check the list
of well-known bugs and, if possible in any way, try a
current CVS development snapshot.
Most users do not compile the GNU C Library from the sources released by the GNU developers. Most people are using glibc binaries supplied with a complete operating system distribution (for a comprehensive list of distributions see Linux Weekly News Distributions page). Distributions include their own modifications to glibc in the binaries and sources you get with the operating system. If the glibc you are using comes from a complete operating system distribution, you should report bugs to that distribution project first. Your distribution's own documentation and web pages should refer you to their bug-reporting system. Your distribution's maintainers will determine whether the problem is specific to their modifications or other details of that particular system. If the problem does exist in the standard GNU C Library code, they will report it to the GNU maintainers or direct you how to do so.
If you have determined that your bug should be directed
directly to the GNU developers and not your distribution
maintainers, your next step should be to check the latest CVS
sources. Information on the glibc CVS repository
can be found at the glibc status
As a rule, bug reports should generally be filed against the current CVS versions at the time you file the bug. glibc development can move quickly at times and you will often find your specific bug has already been fixed.
glibc runs a bugzilla database where all bugs should be recorded.
You might save yourself significant effort by simply checking
the problem still exists with current development snapshots (see
the resources page for more
information). Building glibc is a tricky business, and
glibc maintainers will generally not offer generous
support for people having problems building the library.
Your bug may already have been reported. Firstly, use a
general web search engine such as Google to investigate your
problem. Search engines should index many different mailing
lists where others may have explored the same problem.
Secondly, try your search via the search functionality provided at the libc-alpha, libc-hacker and libc-ports information pages (see resources for more relevant mailing lists). These are the main lists where the GNU developers discuss glibc issues.
Finally, use the query existing bug reports and the most frequently reported bugs forms to attempt to identify your bug in Bugzilla. If you find your bug some relevant actions (in increasing order of usefulness) might be
If your bug does not appear to exist, you may file a new bug with the new bug form. Bugzilla contains a general bug writing guide explaining the interface. Please take into account the following guidelines:
Even if you think a bug is new, expert glibc bug hunters may recognise it as a symptom of an existing problem and mark it as duplicate.
Support is broadly divided up into components relating to divisions in the libc source code. Please read the component descriptions and file your bug appropriately.
There are a number of mailing lists relevant to glibc development. Please check the resources page for a complete list.
Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005 Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA
Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
Updated: $Date: 2005/09/22 23:50:38 $ $Author: ianw $