mailing list of musl libc
 help / color / mirror / code / Atom feed
From: David Wuertele <dave+gmane@wuertele.com>
To: musl@lists.openwall.com
Subject: NULL deref SEGV in malloc.c:unbin()
Date: Fri, 27 Dec 2013 18:35:00 +0000 (UTC)	[thread overview]
Message-ID: <loom.20131227T193125-746@post.gmane.org> (raw)

I wonder if anyone has hit this before?   In unbin(), c->next->prev is set, but
c->next is NULL.   It happens repeatedly, and here's what gdb says:

(gdb) b fopen
Breakpoint 9 at 0x90f78: file src/stdio/fopen.c, line 13.
(gdb) c
Continuing.

Breakpoint 9, fopen (filename=0xaabe4 "/etc/hosts", mode=0xaabf0 "r")
    at src/stdio/fopen.c:13
13	src/stdio/fopen.c: No such file or directory.
	in src/stdio/fopen.c
(gdb) b unbin
Breakpoint 10 at 0x8bc44: file src/malloc/malloc.c, line 239.
(gdb) c
Continuing.

Breakpoint 10, unbin (c=0x21408b8, i=40) at src/malloc/malloc.c:239
239	src/malloc/malloc.c: No such file or directory.
	in src/malloc/malloc.c
(gdb) print *c
$6 = {psize = 2096, csize = 2097, next = 0x2140088, prev = 0x0}
(gdb) s
241	in src/malloc/malloc.c
(gdb) 
Program received signal SIGSEGV, Segmentation fault.
0x0008bcc0 in unbin (c=0x21408b8, i=40) at src/malloc/malloc.c:241
241	in src/malloc/malloc.c
(gdb) 

The root cause was not obvious on scanning the source.
Is this perhaps something that's already been fixed?

Dave



             reply	other threads:[~2013-12-27 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27 18:35 David Wuertele [this message]
2013-12-27 19:05 ` Rich Felker
2013-12-27 19:44   ` David Wuertele
2013-12-27 22:13     ` Rich Felker
2013-12-28  0:25       ` David Wuertele
2013-12-28  1:28         ` David Wuertele
2013-12-28  3:03           ` Rich Felker
2013-12-29  0:01           ` Szabolcs Nagy
2013-12-29  0:05             ` Szabolcs Nagy
2013-12-29  1:34               ` Rich Felker
2013-12-30 19:17             ` David Wuertele
2013-12-30 21:25               ` 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=loom.20131227T193125-746@post.gmane.org \
    --to=dave+gmane@wuertele.com \
    --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).