From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 51B2981F3E for ; Fri, 2 Dec 2016 08:39:06 -0800 (PST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP; 02 Dec 2016 08:39:05 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,287,1477983600"; d="scan'208";a="1076661675" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga001.fm.intel.com with ESMTP; 02 Dec 2016 08:39:05 -0800 Received: from fmsmsx115.amr.corp.intel.com (10.18.116.19) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Fri, 2 Dec 2016 08:39:03 -0800 Received: from fmsmsx103.amr.corp.intel.com ([169.254.2.12]) by fmsmsx115.amr.corp.intel.com ([169.254.4.117]) with mapi id 14.03.0248.002; Fri, 2 Dec 2016 08:39:03 -0800 From: "Carsey, Jaben" To: Tim Lewis , "edk2-devel@lists.01.org" CC: "Ni, Ruiyu" , "Carsey, Jaben" Thread-Topic: [shell] Pipe causes pool failure in Shell.c Thread-Index: AdJMb+c9NhfY6jUuS3GDj+qFTwT7ewASVvHA Date: Fri, 2 Dec 2016 16:39:02 +0000 Message-ID: References: <7236196A5DF6C040855A6D96F556A53F410D2D@msmail.insydesw.com.tw> In-Reply-To: <7236196A5DF6C040855A6D96F556A53F410D2D@msmail.insydesw.com.tw> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTZkMzQ0NmQtODZjYi00NWVmLTk0NWItMGEwMTk1OTVkNTJmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkRabmJvVmZZS2NLYUJYN1p4MFJ3TnBUeTFkWXg3UjQyeVRPOThudFVOYWc9In0= x-ctpclassification: CTP_IC x-originating-ip: [10.1.200.107] MIME-Version: 1.0 Subject: Re: [shell] Pipe causes pool failure in Shell.c X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 16:39:06 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Does that leak memory? It looks like that memory was allocated at 1720, th= en 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-bounces@lists.01.org] On Behalf Of > Tim Lewis > Sent: Thursday, December 01, 2016 11:45 PM > To: Tim Lewis ; edk2-devel@lists.01.org > Subject: [edk2] [shell] Pipe causes pool failure in Shell.c > Importance: High >=20 > After looking further, it appears that the FreePool() call on line 1756 i= s > unnecessary, and just causes a breakpoint. >=20 > Removing it allows the functionality to work correctly. >=20 > // FreePool (Split->SplitStdIn); >=20 >=20 > Tim > -----Original Message----- > From: edk2-devel [mailto:edk2-devel-bounces@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 >=20 > Using the latest Shell build, try: >=20 > ls -sfo | parse FileInfo 2 >=20 > This ends up with a breakpoint when FreePool is called on Shell.c, line 1= 756. >=20 > I'm still debugging, but I wondered if anyone else has seen this? >=20 > Also: >=20 > ls -sfo > tmp > parse FileInfo 2 < tmp >=20 > prints nothing, but >=20 > parse tmp FileInfo 2 >=20 > works fine. >=20 > 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