69 lines
3.3 KiB
HTML
69 lines
3.3 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>Glibc 2 HOWTO: Reporting bugs.</TITLE>
|
|
<LINK HREF="Glibc2-HOWTO-10.html" REL=next>
|
|
<LINK HREF="Glibc2-HOWTO-8.html" REL=previous>
|
|
<LINK HREF="Glibc2-HOWTO.html#toc9" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="Glibc2-HOWTO-10.html">Next</A>
|
|
<A HREF="Glibc2-HOWTO-8.html">Previous</A>
|
|
<A HREF="Glibc2-HOWTO.html#toc9">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s9">9. Reporting bugs.</A></H2>
|
|
|
|
<P>
|
|
<!--
|
|
glibc!bugs, reporting
|
|
-->
|
|
<P>If you think the lib is buggy, please read first the FAQ. It might be that
|
|
others had the same problem and there's an easy solution. You should also
|
|
check the section "Recommended Tools to Install the GNU C Library" in the
|
|
<CODE>INSTALL</CODE> file since some bugs are bugs of the tools and not of glibc.
|
|
<P>Once you've found a bug, make sure it's really a bug. A good way to do this
|
|
is to see if the GNU C library behaves the same way some other C library
|
|
does. If so, probably you are wrong and the libraries are right (but not
|
|
necessarily). If not, one of the libraries is probably wrong.
|
|
<P>Next, go to
|
|
<A HREF="http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl">http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl</A>,
|
|
and look through the bug database. Check here to verify the problem has not
|
|
already be reported. You should also look at the file <CODE>BUGS</CODE>
|
|
(distributed with libc) to check for known bugs.
|
|
<P>Once you're sure you've found a new bug, try to narrow it down to the smallest
|
|
test case that reproduces the problem. In the case of a C library, you
|
|
really only need to narrow it down to one library function call, if possible.
|
|
This should not be too difficult.
|
|
<P>The final step when you have a simple test case is to report the bug. When
|
|
reporting a bug, send your test case, the results you got, the results you
|
|
expected, what you think the problem might be (if you've thought of anything),
|
|
your system type, the versions of the GNU C library, the GNU CC compiler, and
|
|
the GNU Binutils which you are using. Also include the files
|
|
<CODE>config.status</CODE> and <CODE>config.make</CODE> which are created by running
|
|
<CODE>configure</CODE>; they will be in whatever directory was current when you
|
|
ran <CODE>configure</CODE>.
|
|
<P>All bug reports for the GNU C library should be sent using the
|
|
<CODE>glibcbug</CODE> shell script which comes with the GNU libc to
|
|
<A HREF="bugs@gnu.org">bugs@gnu.org</A> (the older address
|
|
<A HREF="bugs@gnu.ai.mit.edu">bugs@gnu.ai.mit.edu</A>
|
|
is still working), or submitted through the GNATS web interface at
|
|
<A HREF="http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl">http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl</A>.
|
|
<P>Suggestions and questions should be sent to the mailing list at
|
|
<A HREF="bugs-glibc@prep.ai.mit.edu">bugs-glibc@prep.ai.mit.edu</A>.
|
|
If you don't read the gnewsgroup gnu.bug.glibc, you can subscribe to
|
|
the list by asking
|
|
<A HREF="bug-glibc-request@prep.ai.mit.edu">bug-glibc-request@prep.ai.mit.edu</A>.
|
|
<P>Please DO NOT send bug report for the GNU C library to
|
|
<bug-gcc@prep.ai.mit.edu>. That list is for bug reports for GNU CC.
|
|
GNU CC and the GNU C library are separate entities maintained by
|
|
separate people.
|
|
<P>
|
|
<P>
|
|
<HR>
|
|
<A HREF="Glibc2-HOWTO-10.html">Next</A>
|
|
<A HREF="Glibc2-HOWTO-8.html">Previous</A>
|
|
<A HREF="Glibc2-HOWTO.html#toc9">Contents</A>
|
|
</BODY>
|
|
</HTML>
|