-
Notifications
You must be signed in to change notification settings - Fork 15
/
Copy pathbug_report.html
47 lines (42 loc) · 2.19 KB
/
bug_report.html
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
---
permalink: /bug_report.html
layout: page
title: Report a Bug
header: Report a Bug
group: navigation
---
{% include JB/setup %}
<p>
Before sending a bug-report, you should check the
<a href="{{ site.baseurl }}/FAQ.html">FAQ</a> and
our <a href="https://github.com/CGAL/cgal/issues" target="_blank">issue tracker</a> on GitHub,
where your issue might have already been answered or reported.
<p>
If you are using an old version of CGAL, your problem may have already
been solved in a more recent release. Please try your program with
the <a HREF="{{ site.baseurl }}/releases.html">latest release</a>.
<p>
Bug reports should be made on our <a href="https://github.com/CGAL/cgal/issues" target="_blank">GitHub issue tracker</a>
(Note that this requires you to have a GitHub account).
In your issue, please do include as much information as possible:
<UL>
<LI> a short, self-contained, correct (compilable), example (see <a href="http://sscce.org/" target="_blank">sscce.org</a>), which you should put on <a href="http://gist.github.com" target="_blank">gist.github.com</a>;
<LI> which operating system, compiler, and hardware you are using;
<LI> information about how CGAL was installed on your system
(<I>i.e.</I>, which options were used, how the library was
built, <I>etc.</I>);
<LI> any third-party software (such as GMP) that is involved;
<LI> a description of the problem or bug and a way to reproduce it
(such as a small sample program or a sequence of commands);
<LI> do not forget to mention which kernel you are using, and check
for potential <a href="{{ site.baseurl }}/FAQ.html#kernels">robustness</a> issues
you may have;
<LI> in case of run-time crash, please include a stack trace provided
by the debugger;
<LI> in case of problems with the installation, make sure to include
the install.log file.
</UL>
<p>
The more information you provide, the easier it will be for us to
help you quickly solve the problem.</p>
<a href="https://github.com/CGAL/cgal/issues/new" class="btn" target="_blank">Open an issue on GitHub</a>