Github messages for voidlinux
 help / color / mirror / Atom feed
From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mlocate `mupdatedb -f proc` segfaults on aarch64-musl
Date: Tue, 20 Oct 2020 21:53:33 +0200	[thread overview]
Message-ID: <20201020195333.E2POeY0uTuB1DF1ZFfPkHKlfqFezX3-bKpfRD5PHrL4@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: 2264 bytes --]

New comment by duncancmt on void-packages repository

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

Comment:
I'm re-opening this issue because #25605 did not fix the segfault here. Fortunately, it *did* fix `gdb`, so now I have a backtrace
```
# gdb --args `which mupdatedb` -f proc
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/mupdatedb...
Reading symbols from /usr/lib/debug//usr/bin/mupdatedb...
(gdb) run
Starting program: /usr/bin/mupdatedb -f proc

Program received signal SIGSEGV, Segmentation fault.
0x0000fffff7fa4440 in strcmp (l=0xfffff7ffb5c0 "/boot",
    r=0xffffffffaaace020 <error: Cannot access memory at address 0xffffffffaaace020>) at src/string/strcmp.c:5
5       src/string/strcmp.c: No such file or directory.
(gdb) bt
#0  0x0000fffff7fa4440 in strcmp (l=0xfffff7ffb5c0 "/boot",
    r=0xffffffffaaace020 <error: Cannot access memory at address 0xffffffffaaace020>) at src/string/strcmp.c:5
#1  0x0000aaaaaaaaea94 in filesystem_is_excluded (path=0xfffff7ffb5c0 "/boot") at src/updatedb.c:404
#2  scan (path=0xfffff7ffb5c0 "/boot", cwd_fd=0xfffffffff178, relative=0xaaaaaaacc229 "boot", st_parent=<optimized out>)
    at src/updatedb.c:765
#3  0x0000aaaaaaaaf1d0 in scan_subdirs (st=0xfffffffff180, dir=<synthetic pointer>) at src/updatedb.c:497
#4  scan (path=<optimized out>, cwd_fd=0xfffffffff328, relative=<optimized out>, st_parent=<optimized out>) at src/updatedb.c:825
#5  0x0000aaaaaaaac778 in main (argc=<optimized out>, argv=<optimized out>) at src/updatedb.c:1012
```

  parent reply	other threads:[~2020-10-20 19:53 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 ` [ISSUE] [CLOSED] " duncancmt
2020-10-20 19:53 ` duncancmt [this message]
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=20201020195333.E2POeY0uTuB1DF1ZFfPkHKlfqFezX3-bKpfRD5PHrL4@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).