mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Ivo Palli <>
To: "" <>
Subject: [musl] Musl compiled gawk coredumps. How to find out where?
Date: Fri, 24 Sep 2021 10:41:24 +0000	[thread overview]
Message-ID: <> (raw)

[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]

Hi there,

I compiled gawk-4.2.1 (with gmp-6.2.1 and mpfr-4.1.0) using musl-1.2.2.

Using it with I script I wrote I get

gawk: /.../.../build_total.awk:25: ( FNR=6) fatal error: internal error
./go: line 36: 14488 Aborted                 (core dumped)

Loading it into gdb doesn't give much information:

# gdb -q ./gawk core.gawk.0.51bcaa32ed144d2498e3a70ff28af961.14488.1632479605000000
Reading symbols from ./gawk...done.
[New LWP 14488]
Core was generated by `gawk -i functions.awk -v TEMPLATE=...
Program terminated with signal SIGABRT, Aborted.
#0  0x00000000004cf169 in __restore_sigs ()
(gdb) backtrace
#0  0x00000000004cf169 in __restore_sigs ()
#1  0x00000000004cf1c4 in raise ()
#2  0x0000000000000000 in ?? ()
(gdb) frame 0
#0  0x00000000004cf169 in __restore_sigs ()
(gdb) print
The history is empty.

I compiled gawk the same with regular gcc (version 8.3.1 20190507 (Red Hat 8.3.1-4)) into a dynamic binary with the same libraries, and that did complete my script without crashing.

Can anybody inform me how to find out exactly where the crash occurs and how I can help fix this bug?


   Ivo Palli

[-- Attachment #2: Type: text/html, Size: 3200 bytes --]

             reply	other threads:[~2021-09-24 10:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 10:41 Ivo Palli [this message]
2021-09-24 12:37 ` Rich Felker
2021-09-24 13:02   ` Ivo Palli
2021-09-24 13:48     ` Rich Felker
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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

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).