From: Tim Lewis <tim.lewis@insyde.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Pipe causes pool failure in Shell.c
Date: Fri, 2 Dec 2016 01:47:42 +0000 [thread overview]
Message-ID: <7236196A5DF6C040855A6D96F556A53F410B90@msmail.insydesw.com.tw> (raw)
Using the latest Shell build, try:
ls -sfo | parse FileInfo 2
This ends up with a breakpoint when FreePool is called on Shell.c, line 1756.
I'm still debugging, but I wondered if anyone else has seen this?
Also:
ls -sfo > tmp
parse FileInfo 2 < tmp
prints nothing, but
parse tmp FileInfo 2
works fine.
Tim
reply other threads:[~2016-12-02 1:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-list 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=7236196A5DF6C040855A6D96F556A53F410B90@msmail.insydesw.com.tw \
--to=devel@edk2.groups.io \
/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