From: Rich Felker <dalias@libc.org>
To: Ivo Palli <Ivo.Palli@bytesnet.nl>
Cc: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: [musl] Musl compiled gawk coredumps. How to find out where?
Date: Fri, 24 Sep 2021 09:48:58 -0400 [thread overview]
Message-ID: <20210924134857.GG13220@brightrain.aerifal.cx> (raw)
In-Reply-To: <PR1PR07MB49085E8B6F80D1485FA776F0F6A49@PR1PR07MB4908.eurprd07.prod.outlook.com>
On Fri, Sep 24, 2021 at 01:02:27PM +0000, Ivo Palli wrote:
> That helped!
>
> (gdb) backtrace
> #0 __restore_sigs (set=set@entry=0x7fff62ee5de0) at ./arch/x86_64/syscall_arch.h:40
> #1 0x00000000004cf1c4 in raise (sig=sig@entry=6) at src/signal/raise.c:11
> #2 0x00000000004c96ea in abort () at src/exit/abort.c:11
> #3 0x0000000000452f16 in catchsig (sig=<optimized out>) at main.c:1231
> #4 catchsig (sig=<optimized out>) at main.c:1217
> #5 <signal handler called>
> #6 get_meta (p=p@entry=0x7f4d35d74f50 "\260\232\243\001") at src/malloc/mallocng/meta.h:141
> #7 0x00000000004ca62c in __libc_free (p=0x7f4d35d74f50) at src/malloc/mallocng/free.c:105
> #8 0x0000000000459d57 in r_unref (tmp=tmp@entry=0x7f4d35f5c778) at node.c:492
> #9 0x00000000004456e5 in unref (r=0x7f4d35f5c778) at awk.h:1898
> #10 purge_record () at field.c:360
> #11 0x0000000000445f36 in set_record (
> buf=0x7f4d34f34cfe "SIZE\t1KB\t192758\t112698119\nSIZE\t4KB\t462090\t1122421206\nSIZE\t16KB\t355596\t3138948391\nSIZE\t64KB\t413028\t13558910172\nSIZE\t256KB\t1014012\t165385758947\nSIZE\t1MB\t2546508\t1346405498466\nSIZE\t10MB\t480844\t1602796961"..., cnt=25, fw=0x0) at field.c:269
> #12 0x000000000044e765 in inrec (iop=<optimized out>, errcode=errcode@entry=0x7fff62ee6cb0) at io.c:608
> #13 0x00000000004414f8 in h_interpret (code=<optimized out>) at interpret..h:1289
> #14 0x0000000000402631 in main (argc=<optimized out>, argv=<optimized out>) at main.c:516
>
> Little unsure where gawk stops and musl begins. I guess #6 is where
> it goes wrong. Any musl developer want to work with me to figure
> this out?
Line 141 of meta.h is catching double-free. This is almost surely a
bug in gawk, potentially a serious one. Running under valgrind might
tell you more about where the corresponding alloc and previous free
occurred.
Rich
next prev parent reply other threads:[~2021-09-24 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 10:41 Ivo Palli
2021-09-24 12:37 ` Rich Felker
2021-09-24 13:02 ` Ivo Palli
2021-09-24 13:48 ` Rich Felker [this message]
2021-09-24 13:48 Érico Nogueira
2021-09-24 14:38 ` Ivo Palli
2021-09-24 14:53 ` Ivo Palli
2021-09-24 15:39 ` 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=20210924134857.GG13220@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=Ivo.Palli@bytesnet.nl \
--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).