# バグの報告

## Bug Tracker <a href="#bug-tracker" id="bug-tracker"></a>

For reporting any kind of bugs, use the [GitHub issue tracker](https://github.com/LMMS/lmms/issues). Please take a look at other [submitted bugs](https://github.com/LMMS/lmms/issues) before opening a new item as someone else might have reported the same bug.

## Reporting Bugs with `gdb` <a href="#gdb" id="gdb"></a>

If you are using LMMS and encounter a segmentation fault (crash), please include a full backtrace:

{% tabs %}
{% tab title="Linux" %}

```
gdb /usr/bin/lmms
r
```

Then attempt to replicate the crash. Once LMMS crashes:

```
thread apply all backtrace
```

{% endtab %}
{% endtabs %}

The output of this command is interesting for us! Please either report it to the [issue tracker](https://github.com/LMMS/lmms/issues) or email it to the [mailing list](http://lists.sourceforge.net/lists/listinfo/lmms-devel).

## How to Report Bugs without GDB <a href="#reporting-bugs-without-gdb" id="reporting-bugs-without-gdb"></a>

{% tabs %}
{% tab title="Linux" %}

```
$ ulimit -l unlimited
$ lmms
```

Now when LMMS crashes, there will be a file called "core" in your working directory. The file may be large enough to be worth zipping.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lmms.io/user-manual/jp_2/getting-started/reporting-a-bug.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.