Github messages for voidlinux
 help / color / mirror / Atom feed
From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] mlocate `mupdatedb -f proc` segfaults on aarch64-musl
Date: Mon, 12 Oct 2020 03:04:05 +0200	[thread overview]
Message-ID: <20201012010405.m9X_tPK6d1Q_oEHmqX8rcVvNlkd7P6xkv1P_b-piUEw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25531@inbox.vuxu.org>

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

Closed issue by duncancmt on void-packages repository

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

Description:
Yet another report in my "PACKAGE segfaults on aarch64-musl" series. See also #24783 #24785 #24918 and #25125 (more to come, I'm sure).

### System

* xuname:  
  *Void 5.7.0_1 aarch64-musl Unknown uptodate rrFFFFF*
* package:  
  *mlocate-0.26_4*

### Expected behavior

```
# mupdatedb -f proc
# echo $?
0
```

### Actual behavior

```
# mupdatedb -f proc
Segmentation fault
```

### Steps to reproduce the behavior

See above

### Other remarks

```
# mupdate
# echo $?
0
```

Omitting the `-f proc` flag fixes the problem. I regret that I cannot post a traceback here. `gdb` itself suffers from a probably-related segfault (see #24785).

  parent reply	other threads:[~2020-10-12  1:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-11 19:29 [ISSUE] " duncancmt
2020-10-11 19:46 ` ericonr
2020-10-11 19:52 ` duncancmt
2020-10-11 20:05 ` ericonr
2020-10-12  1:04 ` duncancmt
2020-10-12  1:04 ` duncancmt [this message]
2020-10-20 19:53 ` duncancmt
2020-10-26 15:28 ` sgn
2020-10-26 15:43 ` [ISSUE] [CLOSED] " sgn

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=20201012010405.m9X_tPK6d1Q_oEHmqX8rcVvNlkd7P6xkv1P_b-piUEw@z \
    --to=duncancmt@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).