shithub: aacenc

ref: 999b02adc5b52d8ddf09c9d6f340d9edbb62e4b2
dir: /common/libsndfile/doc/bugs.html/

View raw version
<HTML>

<HEAD>
	<TITLE>
	Bug Reporting
	</TITLE>
	<META NAME="Author"      CONTENT="Erik de Castro Lopo (erikd@zip.com.au)">
</HEAD>

<BODY TEXT="#FFFFFF" BGCOLOR="#000000" LINK="#9090FF" VLINK="#5050FF" ALINK="#FF00FF">

<FONT SIZE=3>

<FONT SIZE=+20 COLOR="#5050FF">
	<BR>
	<CENTER>
		<B>Reporting Bugs in libsndfile</B>
	</CENTER>
</FONT>

<BR><BR>
	I am interested in finding and fixing all genuine bugs in libsndfile. Bugs I want to
	fix include	any of the following problems (and probably others) :
	<UL>
	<LI>	compilation problems on new platforms
	<LI>	errors being detected during the `make check' process
	<LI>	segmentation faults occuring inside libsndfile
	<LI>	libsndfile hanging when opening a file
	<LI>	supported sound file types being incorrectly read or written
	<LI>	errors or spelling mistakes in the documentation
	</UL>
	
<BR>
	When submitting a bug report you must include :
	<UL>
	<LI>	the operating system you are using
	<LI>	the compiler you are using 
	<LI>	a description of the problem
	<LI>	information generated by the sfinfo program (see next paragraph)
	</UL>
	
<BR>
	If libsndfile compiles and installs correctly but has difficulty reading a particular 
	file or type of file you should run the <B>sfinfo</B> program (from the examples 
	directory of the libsndfile distribution) on the file. See 
		<A HREF="sfinfo.html">here</A>
	for an example of the use of the <B>sfinfo</B> program.

<BR><BR>
	Please do not send me a sound file which fails to open under libsndfile unless I
	specifically ask you to. The above information should usually suffice for most
	problems.
	
<BR><BR>
	Once you have the above information you may mail it to me at
		 <A HREF="mailto:erikd@zip.com.au">erikd@zip.com.au</a>.

<BR><BR>
</FONT>
</BODY>
</HTML>