public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Bug report: Core dump with too many args
Date: Wed, 07 Nov 2018 19:36:00 -0000	[thread overview]
Message-ID: <87d0rgd6jh.fsf@Rainer.invalid> (raw)
In-Reply-To: <acb82352c5c3419e80dd9565c4d74240@prosa.dk> (Ole Tange's message	of "Wed, 7 Nov 2018 13:37:53 +0000")

Ole Tange writes:
> I get core dump when running:
>
> $ /bin/echo `seq 1000000`
> Segmentation fault (core dumped)
>
> This also looks bad:
>
> $ /bin/wc `seq 1000000`
>       2 [main] -bash 15396 C:\cygwin\bin\bash.exe: *** fatal error - cmalloc would have returned NULL
> Hangup

They both just segfault with a stacktrace on my work laptop.  OTOH, both
succeed on our server, which admittedly has much more physical memory
(128GB), with lots of it free while I ran the commands.

So I guess the only real complaint is that the out-of-memory condition
should take precedence over other faults, or did you have something else
in mind?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      parent reply	other threads:[~2018-11-07 19:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 13:38 Ole Tange
2018-11-07 15:04 ` Steven Penny
2018-11-07 19:36 ` Achim Gratz [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=87d0rgd6jh.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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.
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).