From: Eric Blake <eblake@redhat.com>
To: Dan Kegel <dank@kegel.com>
Cc: dash@vger.kernel.org
Subject: Re: Crash on valid input
Date: Mon, 08 Apr 2013 21:27:28 -0600 [thread overview]
Message-ID: <51638AA0.4080701@redhat.com> (raw)
In-Reply-To: <CAPF-yOZmkcKSpU+jVMsSi6Q8harUYZ-hS5Ugn7SsbBwm-GzhiQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
On 04/08/2013 09:12 PM, Dan Kegel wrote:
> Yes, my script was crap, I've fixed it.
>
> Here's the reproducer. Called with foo unset. I think it doesn't
> crash without -x.
>
> #!/bin/dash
> set -x
> test ! $foo
The 'set -x' was indeed the key to reproducing the problem. In fact,
this is the shortest I could make it:
dash -cx 'test !'
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]
next prev parent reply other threads:[~2013-04-09 3:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 2:43 Crash on valid input Dan Kegel
2013-04-09 3:08 ` Eric Blake
2013-04-09 3:12 ` Dan Kegel
2013-04-09 3:27 ` Eric Blake [this message]
2013-04-09 3:34 ` Eric Blake
2013-04-09 3:44 ` Dan Kegel
2013-04-09 21:20 ` Harald van Dijk
2013-08-23 11:59 ` Herbert Xu
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=51638AA0.4080701@redhat.com \
--to=eblake@redhat.com \
--cc=dank@kegel.com \
--cc=dash@vger.kernel.org \
/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