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
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head> <link rel="canonical" href="http://www.mcs.anl.gov/petsc/petsc-current/docs/bugreporting.html" />
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>Questions and Bug Reports</title>
</head>
<body bgcolor="#ffffff">
<div id="version" align=right><b>petsc-3.4.2 2013-07-02</b></div>
<h1>Questions and Bug Reports</h1>
<div id="main">
<p>
The PETSc maintenance e-mail, <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a>,
is intended for users to
</p>
<ul>
<li>report bugs,</li>
<li>ask for clarification,</li>
<li>ask for help in tracking down bugs, and</li>
<li>request new features within PETSc.</li>
</ul>
<p>
We respond to almost all email the same day and many within the hour.
<em>Please do not send maintenance requests to the individual PETSc
authors; all e-mail to <a href="mailto:petsc-maint@mcs.anl.gov">petsc-maint@mcs.anl.gov</a>
is automatically distributed to all of the PETSc authors, so our
response time using this address will be fastest.</em>
</p>
<p>
Before sending a bug report, please consult the <a href="faq.html">FAQ</a>
to determine whether a fix or work-around to the problem already exists.
Also, see the chapter
<a href="http://www.mcs.anl.gov/petsc/petsc-dev/docs/manual.pdf#nameddest=ch_performance">Hints for Performance Tuning</a>
in the PETSc users manual for guidelines on achieving good efficiency within PETSc codes.
</p>
<h3>Guidelines for Bug Reports</h3>
<p>
The more information that you convey about a bug, the easier it will be
for us to target the problem. We suggest providing the following
information:
</p>
<ul>
<li>Please do NOT send winmail.dat Microsoft email attachments; we cannot read them.</li>
<li>Please do NOT stick huge files like configure.log DIRECTLY into the email message; instead, make them attachments.</li>
<li>If the problem involves installation, send <u><b>the entire configure.log and make.log</b></u> as attachments.</li>
<li>Machine type: (e.g., sun4)</li>
<li>OS Version: (run <code>uname -a</code> to get the version number)</li>
<li>
PETSc Version: (run PETSc program with -v, or look in
<a href="/usr/lib/petscdir/3.3/include/petscversion.h">include/petscversion.h</a>)
</li>
<li>MPI implementation: (e.g., MPICH, LAM, IBM, SGI)</li>
<li>Compiler: (e.g., Gnu C, Gnu g++, native C)</li>
<li>Probable PETSc component: (for example, <code>Mat, Vec, Draw, KSP</code>, etc.) </li>
<li>Problem description: Also, please cut and paste error messages from the compiler, program, etc.</li>
</ul>
</div>
</body>
</html>
|
