From: ernieIzde8ski <ernieIzde8ski@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] openmw: gdb required for crash logs
Date: Thu, 24 Nov 2022 05:23:38 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40721@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
New 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`
next reply other threads:[~2022-11-24 4:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 4:23 ernieIzde8ski [this message]
2022-11-24 15:26 ` loreb
2022-11-24 16:45 ` paper42
2022-11-25 12:36 ` dataCobra
2022-11-27 12:57 ` ernieIzde8ski
2022-11-27 12:57 ` [ISSUE] [CLOSED] " ernieIzde8ski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40721@inbox.vuxu.org \
--to=ernieizde8ski@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).