Does that leak memory? It looks like that memory was allocated at 1720, then moved from Out to In at 1729-1735.
Did the pointer possibly get mangled at 1724 or somewhere in between? Ray, Have you seen this? -Jaben > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Tim Lewis > Sent: Thursday, December 01, 2016 11:45 PM > To: Tim Lewis <tim.le...@insyde.com>; edk2-devel@lists.01.org > Subject: [edk2] [shell] Pipe causes pool failure in Shell.c > Importance: High > > After looking further, it appears that the FreePool() call on line 1756 is > unnecessary, and just causes a breakpoint. > > Removing it allows the functionality to work correctly. > > // FreePool (Split->SplitStdIn); > > > Tim > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-boun...@lists.01.org] On Behalf Of > Tim Lewis > Sent: Thursday, December 01, 2016 5:48 PM > To: edk2-devel@lists.01.org > Subject: [edk2] Pipe causes pool failure in Shell.c > > 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 > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel > _______________________________________________ > edk2-devel mailing list > edk2-devel@lists.01.org > https://lists.01.org/mailman/listinfo/edk2-devel _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
