celluloid-player.github.io/bug-reports.html at master · celluloid-player/celluloid-player.github.io · GitHub

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
77
78
79
80
81
<!-- vim: set ts=4 sw=4: !-->
<!DOCTYPE html>
<html>
	<head>
		<title>Celluloid - Bug Reports</title>
		<link rel="stylesheet" type="text/css" href="stylesheets/main.css">
		<link rel="shortcut icon" href="images/favicon.png">
	</head>
	<body>
		<div class="navbar-bg">
			<div class="navbar">
				<a class="navitem" href="index.html">
					<div class="navitem">
						Home
					</div>
				</a>
				<a class="navitem" href="installation.html">
					<div class="navitem">
						Installation
					</div>
				</a>
				<div class="navitem current-navitem">
					Bug Reports
				</div>
				<a class="navitem" href="faq.html">
					<div class="navitem">
						FAQ
					</div>
				</a>
			</div>
		</div>

		<div class="content">
			<h2>Bug Reports</h2>
			<p>
				Questions, bug reports, and feature requests can be reported via the
				<a href="https://github.com/celluloid-player/celluloid/issues">issue
				tracker</a>.
			</p>

			<p>
				When reporting bugs:
				<div>
					<ul>
<li>Make sure you're using the latest release.</li>
<li>If possible, also check if the problem has already been fixed in git master.</li>
<li>Don't report multiple unrelated/barely related bugs in one issue.</li>
<li>Attach a log file.
<ul>
<li>You can make Celluloid print log messages by running
<code>G_MESSAGES_DEBUG=all celluloid --mpv-msg-level=all=trace</code>
</li>
<li>The command above will cause Celluloid to generate a large amount of
log messages, so you may also want to redirect the output to a file.
For example, you can redirect log messages to <code>/tmp/celluloid.log</code>
with this command:
<code>G_MESSAGES_DEBUG=all celluloid --mpv-msg-level=all=trace &amp;&gt; /tmp/celluloid.log</code>.</li>
</ul>
</li>
<li>If the issue involves crashing, include a backtrace in the report.
<ul>
<li>You can create a backtrace by running
<code>gdb -ex 'set pagination off' -ex run -ex bt celluloid</code>
and perform the action that triggers the crash.</li>
</ul>
</li>
<li>If the issue is a regression, it would be very helpful if you could perform a
<a href="https://git-scm.com/docs/git-bisect" rel="nofollow">bisect</a> to locate the commit that
introduces the regression.</li>
</ul>

				</div>
			</p>
		</div>

		<div class="footer">
			Copyright &copy; 2018-2022 gnome-mpv.
			This webpage is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike 4.0 International License</a>.
		</div>
	</body>
</html>