hey! this is a static git repo viewer. commit diffs, file history, older commits and other revisions won't load without javascript.

you are still able to view source files on branch/tag tips, but the experience is degraded.

char-fork/llama.cpp

git clone https://git.t4t.associates/char-fork/llama.cpp

Johannes Gäßlergithub: mention --log-file in issue templates (#23277)a8078675a2026-05-19

1name: Bug (misc.)
2description: Something is not working the way it should (and it's not covered by any of the above cases).
3title: "Misc. bug: "
4labels: ["bug-unconfirmed"]
5body:
6  - type: markdown
7    attributes:
8      value: >
9        Thanks for taking the time to fill out this bug report!
10        This issue template is intended for miscellaneous bugs that don't fit into any other category.
11        If you encountered the issue while using an external UI (e.g. ollama),
12        please reproduce your issue using one of the examples/binaries in this repository.
13
14        Please fill out this template yourself, copypasting language model outputs is [strictly prohibited](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md#ai-usage-policy).
15  - type: textarea
16    id: version
17    attributes:
18      label: Name and Version
19      description: Which version of our software is affected? (You can use `--version` to get a version string.)
20      placeholder: |
21        $./llama-cli --version
22        version: 2999 (42b4109e)
23        built with cc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0 for x86_64-linux-gnu
24    validations:
25      required: true
26  - type: dropdown
27    id: operating-system
28    attributes:
29      label: Operating systems
30      description: Which operating systems do you know to be affected?
31      multiple: true
32      options:
33        - Linux
34        - Mac
35        - Windows
36        - BSD
37        - Other? (Please let us know in description)
38    validations:
39      required: false
40  - type: dropdown
41    id: module
42    attributes:
43      label: Which llama.cpp modules do you know to be affected?
44      multiple: true
45      options:
46        - Documentation/Github
47        - libllama (core library)
48        - llama-cli
49        - llama-server
50        - llama-bench
51        - llama-quantize
52        - Python/Bash scripts
53        - Test code
54        - Other (Please specify in the next section)
55    validations:
56      required: false
57  - type: textarea
58    id: command
59    attributes:
60      label: Command line
61      description: >
62        Please provide the exact commands you entered, if applicable. For example: `llama-server -m ... -c ...`, `llama-cli -m ...`, etc.
63        This will be automatically formatted into code, so no need for backticks.
64      render: shell
65    validations:
66      required: false
67  - type: textarea
68    id: info
69    attributes:
70      label: Problem description & steps to reproduce
71      description: >
72        Please give us a summary of the problem and tell us how to reproduce it (if applicable).
73    validations:
74      required: true
75  - type: textarea
76    id: first_bad_commit
77    attributes:
78      label: First Bad Commit
79      description: >
80        If the bug was not present on an earlier version and it's not trivial to track down: when did it start appearing?
81        If possible, please do a git bisect and identify the exact commit that introduced the bug.
82    validations:
83      required: false
84  - type: textarea
85    id: logs
86    attributes:
87      label: Relevant log output
88      description: >
89          If applicable, please copy and paste any relevant log output, including any generated text.
90          If you are encountering problems specifically with the `llama_params_fit` module, always upload `--verbose` logs as well.
91          For very long logs (thousands of lines), please upload them as files instead; the `--log-file` CLI argument can be used for this purpose.
92          On Linux you can alternatively redirect the console output of any command into a file by appending ` > llama.log 2>&1` to your command.
93      value: |
94        <details>
95        <summary>Logs</summary>
96        <!-- Copy-pasted short logs go into the "console" area here -->
97
98        ```console
99
100        ```
101        </details>
102
103        <!-- Long logs that you upload as files go here, outside the "console" area -->
104    validations:
105      required: false