Reporting Bugs; Have You Found A Bug; How To Report Bugs - Red Hat ENTERPRISE LINUX 3 - USING ID Using Instructions

Your bug reports play an essential role in making
Reporting a bug may help you by bringing a solution to your problem, or it may not. But in any case
the principal function of a bug report is to help the entire community by making the next version of
work better. Bug reports are your contribution to the maintenance of
ld
In order for a bug report to serve its purpose, you must include the information that enables us to fix
the bug.

7.1. Have You Found a Bug?

If you are not sure whether you have found a bug, here are some guidelines:
If the linker gets a fatal signal, for any input whatever, that is a
•
If produces an error message for valid input, that is a bug.
• ld
If does not produce an error message for invalid input, that may be a bug. In the general case,
• ld
the linker can not verify that object files are correct.
If you are an experienced user of linkers, your suggestions for improvement of
•
any case.

7.2. How to Report Bugs

A number of companies and individuals offer support for gnu products. If you obtained
support organization, we recommend you contact that organization first.
You can find contact information for many support companies and individuals in the file
in the gnu Emacs distribution.
etc/SERVICE
Otherwise, send bug reports for
The fundamental principle of reporting bugs usefully is this: report all the facts. If you are not sure
whether to state a fact or leave it out, state it!
Often people omit facts because they think they know what causes the problem and assume that some
details do not matter. Thus, you might assume that the name of a symbol you use in an example does
not matter. Well, probably it does not, but one cannot be sure. Perhaps the bug is a stray memory
reference which happens to fetch from the location where that name is stored in memory; perhaps, if
the name were different, the contents of that location would fool the linker into doing the right thing
despite the bug. Play it safe and give a specific, complete example. That is the easiest thing for you to
do, and the most helpful.
Keep in mind that the purpose of a bug report is to enable us to fix the bug if it is new to us. Therefore,
always write your bug reports on the assumption that the bug has not been reported previously.
Sometimes people give a few sketchy facts and ask, "Does this ring a bell?" This cannot help us fix
a bug, so it is basically useless. We respond by asking for enough details to enable us to investigate.
You might as well expedite matters by sending them to begin with.
To enable us to fix the bug, you should include all these things:
The version of .
• ld
to
ld bug-binutils@gnu.org
announces it if you start it with the
ld

Reporting Bugs

reliable.
ld
bug. Reliable linkers never crash.
ld
.
-version
Chapter 7.
.
ld
are welcome in
ld
ld
argument.
from a