From: xandkar <xandkar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] collectd segfaults on launch
Date: Fri, 12 Mar 2021 15:11:51 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29413@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
New issue by xandkar on void-packages repository
https://github.com/void-linux/void-packages/issues/29413
Description:
### System
* xuname:
`Void 5.10.23_1 x86_64 AuthenticAMD uptodate rFFFF`
* package:
`collectd-5.12.0_3`
### Expected behavior
Collectd service starts without crashing.
### Actual behavior
Collectd segfaults on start.
### Steps to reproduce the behavior
Install package:
```
# xbps-install collectd
```
Watch dmesg in terminal A:
```
# dmesg --follow
```
Enable collectd service in terminal B
```
# ln -s /etc/sv/collectd /var/service/
```
Observe segfault messages in terminal A, such as:
```
...
[ 336.630494] collectd[6990]: segfault at 14 ip 00007f79c4ec4c99 sp 00007fffedc6adf0 error 4 in libc-2.32.so[7f79c4e06000+14a000]
[ 336.630497] Code: 39 d5 0f 8e d1 01 00 00 48 63 c2 eb 15 0f 1f 40 00 8d 56 01 48 83 c0 01 89 13 39 c5 0f 8e b7 01 00 00 49 8b 0c c4 89 c6 89 c2 <80> 39 2d 75 e2 80 79 01 00 74 dc 8b 03 89 53 30 e9 26 fe ff ff 66
...
```
ATTN: @stpx
next reply other threads:[~2021-03-12 14:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 14:11 xandkar [this message]
2021-03-12 20:09 ` ericonr
2021-03-12 23:35 ` xandkar
2021-03-13 0:01 ` ericonr
2021-03-13 1:20 ` xandkar
2021-03-14 14:00 ` xandkar
2021-03-14 14:43 ` ericonr
2021-03-14 15:10 ` leahneukirchen
2021-03-14 17:45 ` xandkar
2021-03-14 22:02 ` ericonr
2021-03-15 9:07 ` xandkar
2021-03-15 9:09 ` xandkar
2021-03-15 9:16 ` xandkar
2021-03-15 9:16 ` xandkar
2021-09-24 18:27 ` ericonr
2022-05-07 2:06 ` github-actions
2022-05-10 2:47 ` [ISSUE] [CLOSED] " ericonr
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-29413@inbox.vuxu.org \
--to=xandkar@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).