From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Ed Morton <mortoneccc@comcast.net>
Subject: Re: Fwd: gawk core dumped on too many input values
Date: Mon, 28 Aug 2023 17:38:28 +0900 [thread overview]
Message-ID: <20230828173828.bfc011a1cf2b83f341335003@nifty.ne.jp> (raw)
In-Reply-To: <0b55205e-fc7c-98cf-c186-783e5c0655b0@comcast.net>
On Sun, 27 Aug 2023 13:24:55 -0500
Ed Morton wrote:
> This (original email below) turned out to be a general cygwin issue, not
> a gawk issue:
>
> $ LC_ALL=C sed 's/x/y/' $(seq 1000000)
> Segmentation fault (core dumped)
>
> $ LC_ALL=C grep 'foo' $(seq 1000000)
> Segmentation fault (core dumped)
>
> Regards,
>
> Ed.
>
> -------- Forwarded Message --------
> Subject: gawk core dumped on too many input values
> Date: Sun, 27 Aug 2023 08:09:54 -0500
> From: Ed Morton <mortoneccc@comcast.net>
> To: bug-gawk@gnu.org <bug-gawk@gnu.org>
>
>
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: cygwin
> Compiler: gcc
> Compilation CFLAGS: -ggdb -O2 -pipe -Wall -Werror=format-security
> -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong
> --param=ssp-buffer-size=4
> -fdebug-prefix-map=/cygdrive/d/a/scallywag/gawk/gawk-5.2.2-1.x86_64/build=/usr/src/debug/gawk-5.2.2-1
> -fdebug-prefix-map=/cygdrive/d/a/scallywag/gawk/gawk-5.2.2-1.x86_64/src/gawk-5.2.2=/usr/src/debug/gawk-5.2.2-1
> -DNDEBUG
> uname output: CYGWIN_NT-10.0-22621 TournaMart_2023 3.4.8-1.x86_64
> 2023-08-17 17:02 UTC x86_64 Cygwin
> Machine Type: x86_64-pc-cygwin
>
> Gawk Version: 5.2.2
>
> Attestation 1:
> I have read
> https://www.gnu.org/software/gawk/manual/html_node/Bugs.html.
> Yes
>
> Attestation 2:
> I have not modified the sources before building gawk.
> True
>
> Description:
> I was trying to test something related to ARG_MAX when I ran the
> awk script below and it core dumped instead of reporting an error
> and exiting gracefully. In case it's useful getconf ARG_MAX outputs
> 32000.
>
> Repeat-By:
> $ LC_ALL=C awk 'BEGIN{print ARGC}' $(seq 1000000)
> Segmentation fault (core dumped)
Thanks for the report.
I will submit a patch for this issue shortly.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2023-08-28 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e0fa509d-890a-2db7-c91f-2b1d904a9a1e@comcast.net>
2023-08-27 18:24 ` Ed Morton
2023-08-27 23:07 ` Jeremy Hetzler
2023-08-28 11:47 ` Joshuah Hurst
2023-08-28 18:20 ` Brian Inglis
2023-08-29 13:03 ` Corinna Vinschen
2023-08-28 8:38 ` Takashi Yano [this message]
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=20230828173828.bfc011a1cf2b83f341335003@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=mortoneccc@comcast.net \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).