File: bugs.html

package info (click to toggle)
libsndfile 1.0.28-6
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 7,300 kB
  • sloc: ansic: 58,468; sh: 4,783; cpp: 639; makefile: 407; python: 299
file content (76 lines) | stat: -rw-r--r-- 2,706 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>

<HEAD>
	<TITLE>
	Bug Reporting
	</TITLE>
	<META NAME="Author"      CONTENT="Erik de Castro Lopo (erikd AT mega-nerd DOT com)">
	<LINK REL="stylesheet" HREF="libsndfile.css" TYPE="text/css" MEDIA="all">
	<LINK REL="stylesheet" HREF="print.css" TYPE="text/css" MEDIA="print">
</HEAD>

<BODY>

<CENTER>
		<H1><B>Reporting Bugs in libsndfile</B></H1>
</CENTER>
<P>
	Before even attempting to report a bug in libsndfile please make sure you have
	read the
		<A HREF="FAQ.html">Frequently Asked Questions</A>.
	If you are having a problem writing code using libsndfile make sure you read
	the
		<A HREF="api.html">Application Programming Interface</A>
	documentation.
</P>
<P>
	That said, 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) :
</P>
	<UL>
	<LI>	Compilation problems on new platforms.
	<LI>	Errors being detected during the `make check' process.
	<LI>	Segmentation faults occurring inside libsndfile.
	<LI>	libsndfile hanging when opening a file.
	<LI>	Supported sound file types being incorrectly read or written.
	<LI>	Omissions, errors or spelling mistakes in the documentation.
	</UL>

<P>
	When submitting a bug report you must include :
</P>
	<UL>
	<LI>	Your system (CPU and memory size should be enough).
	<LI>	The operating system you are using.
	<LI>	Whether you are using a package provided by your distribution or you
			compiled it youself.
	<LI>	If you compiled it yourself, the compiler you are using. (Also make
			sure to run 'make check'.)
	<LI>	A description of the problem.
	<LI>	Information generated by the sndfile-info program (see next paragraph).
	<LI>	If you are having problems with sndfile-play and ALSA on Linux, I will
			need information about your kernel, ALSA version, compiler version,
			whether you compiled the kernel/ALSA your self or installed from a
			package etc.
	</UL>

<P>
	If libsndfile compiles and installs correctly but has difficulty reading a particular
	file or type of file you should run the <B>sndfile-info</B> program (from the examples
	directory of the libsndfile distribution) on the file. See
		<A HREF="sndfile_info.html">here</A>
	for an example of the use of the <B>sndfile-info</B> program.
</P>
<P>
	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.
</P>
<P>
	Once you have the above information you should submit a ticket on the libsnfile
		<A HREF="https://github.com/erikd/libsndfile/issues">github issue tracker</A>.

</P>
</BODY>
</HTML>