[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210924123717.GE13220@brightrain.aerifal.cx>
Date: Fri, 24 Sep 2021 08:37:17 -0400
From: Rich Felker <dalias@...c.org>
To: Ivo Palli <Ivo.Palli@...esnet.nl>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: Re: Musl compiled gawk coredumps. How to find out where?
On Fri, Sep 24, 2021 at 10:41:24AM +0000, Ivo Palli wrote:
> 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: (FILENAME=big.report 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.
> (gdb)
>
> 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?
Try with musl and gawk built with debug info. If you're running with
musl provided by your distro, it probably has a debug symbols package
you can install. If you're building musl yourself, add --enable-debug
to configure command line or -g to CFLAGS manually.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
