From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/12893 Path: news.gmane.org!.POSTED!not-for-mail From: Rich Felker Newsgroups: gmane.linux.lib.musl.general Subject: Re: SIGSEGV and SIGILL at malloc/free on ARM926 Date: Mon, 4 Jun 2018 05:41:29 -0400 Message-ID: <20180604094129.GY1392@brightrain.aerifal.cx> References: <01af059f-bbab-4f3f-9c45-43f8802999c8.xulu@allwinnertech.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1528105179 15220 195.159.176.226 (4 Jun 2018 09:39:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 4 Jun 2018 09:39:39 +0000 (UTC) User-Agent: Mutt/1.5.21 (2010-09-15) To: musl@lists.openwall.com Original-X-From: musl-return-12909-gllmg-musl=m.gmane.org@lists.openwall.com Mon Jun 04 11:39:35 2018 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1fPlxc-0003rT-Q8 for gllmg-musl@m.gmane.org; Mon, 04 Jun 2018 11:39:32 +0200 Original-Received: (qmail 22195 invoked by uid 550); 4 Jun 2018 09:41:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 22168 invoked from network); 4 Jun 2018 09:41:40 -0000 Content-Disposition: inline In-Reply-To: <01af059f-bbab-4f3f-9c45-43f8802999c8.xulu@allwinnertech.com> Original-Sender: Rich Felker Xref: news.gmane.org gmane.linux.lib.musl.general:12893 Archived-At: On Mon, Jun 04, 2018 at 04:45:28PM +0800, 徐露 wrote: > Hi all, > > I use Openwrt project and the version of musl libc is 1.1.16. > I have been experiencing random crashes when running customer's application. > From the coredump files, the segfault looks like a memory corruption issue. But when I add some malloc and free log, the issues did not occur. > After analyzing several coredump files, I found that the last bit of cszie in chunk has seemed to be set from 1 to 0. > This is very strange and I don't have many ideas how to go further. > Could you please give us some pointers, thanks! I can supply more details as needed. Looks like classic double-free. Rich