From: "A. Wilcox" <awilfox@adelielinux.org>
To: musl@lists.openwall.com
Subject: Re: diffutils crash in malloc
Date: Sun, 12 Nov 2017 15:50:49 -0600 [thread overview]
Message-ID: <5A08C239.4070003@adelielinux.org> (raw)
In-Reply-To: <AM5PR0802MB2611FE5A1F86224DEBDB03FA892A0@AM5PR0802MB2611.eurprd08.prod.outlook.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 12/11/17 15:46, Tobias Koch wrote:
> Hi,
>
> when I switched from musl 1.1.16 to 1.1.17 (and now 1.1.18) diff
> started to crash. The gdb backtrace shows, that this happens
> during memory allocation:
>
> build@bootstrap(mipsel):~$ gdb /tools/bin/diff
[snip]
I notice you are using mipsel. Do you see this on any other
architectures? diffutils compiled against 1.1.16 runs fine against
1.1.17 and 1.1.18 here on x86_64 (64-bit, LE) and ppc (32-bit, BE).
So it seems this may be a MIPS issue.
> Here a and b are empty files, but this happens with other input,
> as well. diffutils' xmalloc looks fairly inconspicuous to me:
>
> I understand this may very well be a problem in diff and not musl.
> But this is the exact same version of diffutils included with
> Debian Stretch and running the same under Valgrind compiled against
> glibc shows no problems. My wisdom ends here. Any clues how I can
> get to the bottom of this?
>
> Tobias
>
Are you using valgrind and glibc on the same hardware (mipsel)?
Best,
- --arw
- --
A. Wilcox (awilfox)
Project Lead, Adélie Linux
http://adelielinux.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJaCMI2AAoJEMspy1GSK50Uk9wQAKPpqdKvQeTFWlUuZesYET1l
8tiHBvWL3vpymOL/cJGyYvlN4rl4TZE+aZrRtxebrgnAV0BwdA0WjNHaWZ0PkRG1
i6Do8GK8pSgYJf9PtgJQLbG+qoGCj9mWDxQm3gxf2r9YGINTOevsbTwfTbvJuFWC
d1DDci7uffIhAQaYMVDm8IOmyOGGcbd91EivF9VZPNoqXcGWg9ZqMiioF+rOngJj
f4Js1YoOHPiweUQWISSIbZffb3Sex5/z5nCRoODm07k4/9ku6BrG/ACeRy5BPSR3
68iDuMahsy6jCScMDgNsWgHvDXqp/XraTF8gPdcER6noq2o98XN+ezy7aUWPWpey
SlhhmFwY3vCTyWU38gPMNw4VPtdaL+yCAy12PZQatHxkK/ck8vlTzqQ8c2FRMibk
vGT85j97MUb/ziA43+9IkGMFc9gBFZdN1T8zNCDl4c7I57cSDvn0NsiJvcFDE+2J
ThJf9ETKrougdJbCo7XIAl/JXSANVnADwd+F04uWYhyWBaA6jOYzOtQbpMM1DdeW
hgnSxmgpwJkWCk4FKufpteeuv37uP8LUeGwjd9mWn18OjDdk092D7SwnaXNAcngp
MsikPC4pzHbKSYUQ4rvHoX/qo4m7Hz9aI65eYcL3CHvX5Cfjlbv+dKI95kBM06ct
Uq1fUeUkpC55II2RlFIp
=kSn0
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2017-11-12 21:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 21:46 Tobias Koch
2017-11-12 21:50 ` A. Wilcox [this message]
2017-11-12 22:02 ` Tobias Koch
2017-11-12 22:24 ` A. Wilcox
2017-11-12 22:38 ` Tobias Koch
2017-11-12 23:05 ` Rich Felker
2017-11-13 19:43 ` Tobias Koch
2017-11-13 20:09 ` Rich Felker
2017-11-13 20:43 ` Tobias Koch
2017-11-13 20:51 ` Rich Felker
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=5A08C239.4070003@adelielinux.org \
--to=awilfox@adelielinux.org \
--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).