From: Andre Renaud <andre@ignavus.net>
To: musl@lists.openwall.com
Subject: Re: seg fault at src/string/strlen.c:15
Date: Wed, 24 Jan 2018 02:33:42 +0000 [thread overview]
Message-ID: <CAEj2-1OzqvGj4WJ-bevSKwfZRx6gD5Ooes6y888_rQfiEVOrHA@mail.gmail.com> (raw)
In-Reply-To: <20180124022743.GX1627@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On Wed, 24 Jan 2018 at 15:28 Rich Felker <dalias@libc.org> wrote:
> On Tue, Jan 23, 2018 at 05:07:32PM -0800, Po-yi Wang wrote:
> > (gdb) run --version
> > Starting program: /tmp/build/make-4.1/make-4.1 --version
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > strlen (s=0x0) at src/string/strlen.c:15
> > 15 for (w = (const void *)s; !HASZERO(*w); w++);
> > (gdb)
>
> This means make is calling strlen(0), so the bug is somewhere else --
> in whatever causing the string pointer passed to strlen to be a null
> pointer. Can you show a full backtrace (bt) rather than just the point
> of the crash?
It's quite possible that this is a known bug in Make 4.1
https://savannah.gnu.org/bugs/?43434
Does it go away if /dev/pts is properly mounted?
Regards,
Andre
[-- Attachment #2: Type: text/html, Size: 1233 bytes --]
next prev parent reply other threads:[~2018-01-24 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 1:07 Po-yi Wang
2018-01-24 2:27 ` Rich Felker
2018-01-24 2:33 ` Andre Renaud [this message]
2018-01-24 2:55 ` Po-yi Wang
2018-01-24 2:55 ` Po-yi Wang
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=CAEj2-1OzqvGj4WJ-bevSKwfZRx6gD5Ooes6y888_rQfiEVOrHA@mail.gmail.com \
--to=andre@ignavus.net \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).