From: Antony Pavlov <antonynpavlov@gmail.com>
To: Wjatscheslaw Stoljarski <wjatscheslaw.stoljarski@kiwigrid.com>
Cc: barebox@lists.infradead.org
Subject: Re: Source command with zero-sized files
Date: Wed, 4 Nov 2015 19:51:49 +0300 [thread overview]
Message-ID: <20151104195149.0883221bdb2163bd9fc82cb5@gmail.com> (raw)
In-Reply-To: <20151104154142.GA27677@gmail.com>
On Wed, 4 Nov 2015 16:41:42 +0100
Wjatscheslaw Stoljarski <wjatscheslaw.stoljarski@kiwigrid.com> wrote:
> Using source command (source <file> or . <file>) on zero-sized files crash barebox.
> Can anyone confirm this?
I can confirm this!
Here is sandbox log:
barebox@barebox sandbox:/ ls -l env/empty
-rwxrwxrwx 0 env/empty
barebox@barebox sandbox:/ source env/empty
Segmentation fault
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-11-04 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 15:41 Wjatscheslaw Stoljarski
2015-11-04 16:51 ` Antony Pavlov [this message]
2015-11-05 6:59 ` [PATCH] hush: Add missing initialize_context() in some places Sascha Hauer
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=20151104195149.0883221bdb2163bd9fc82cb5@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=wjatscheslaw.stoljarski@kiwigrid.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