Re: [ISSUE] [CLOSED] openmw: gdb required for crash logs

[ernieIzde8ski <ernieIzde8ski@users.noreply.github.com>]

[-- Attachment #1: Type: text/plain, Size: 1522 bytes --]

Closed issue by ernieIzde8ski on void-packages repository

https://github.com/void-linux/void-packages/issues/40721

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.9_1 x86_64 AuthenticAMD uptodate rrrmFFFFFFFFFFFF

### Package(s) Affected

openmw-0.47.0_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

OpenMW should be able to generate somewhat detailed crash logs with `gdb` when fatal errors occur. For example, typing `coe 100000 100000` into the console on a vanilla game can generate the following crash log: [https://pastebin.com/NjPHFgsJ](https://pastebin.com/NjPHFgsJ)

### Actual behaviour

Unless `gdb` is already installed, OpenMW is incapable of generating a crash log. A sample from `~/.config/openmw/openmw-crash.log`:

```
*** Fatal Error ***
 (signal 6)
Address: 0x3e800003985

System: Linux vivec 6.0.9_1 #1 SMP PREEMPT_DYNAMIC Fri Nov 18 16:45:48 UTC 2022 x86_64

Executing: gdb --quiet --batch --command=/tmp/gdb-respfile-pfN1ac

Failed to create a crash report. Please make sure that 'gdb' is installed and present in PATH then crash again.
Current PATH: /home/ernie/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
```

### Steps to reproduce

1. Run openmw
2. Do something to cause a fatal crash (entering `coe 100000 100000` onto the in-game console, accessible via backtick by default, should work)
3. Observe `~/.config/openmw/openmw-crash.log`