From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (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 1747521DFA900 for ; Wed, 29 Mar 2017 22:25:26 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP; 29 Mar 2017 22:25:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,245,1486454400"; d="scan'208";a="66754393" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga002.jf.intel.com with ESMTP; 29 Mar 2017 22:25:25 -0700 Received: from fmsmsx116.amr.corp.intel.com (10.18.116.20) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 29 Mar 2017 22:25:25 -0700 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) by fmsmsx116.amr.corp.intel.com (10.18.116.20) with Microsoft SMTP Server (TLS) id 14.3.319.2; Wed, 29 Mar 2017 22:25:25 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.212]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.253]) with mapi id 14.03.0248.002; Thu, 30 Mar 2017 13:25:14 +0800 From: "Fan, Jeff" To: Arka Sharma , "edk2-devel@lists.01.org" Thread-Topic: [edk2] Using Intel UDk debugger Thread-Index: AQHSqRShIGYV4mIab0mtY5ucJOjCKqGs10iA Date: Thu, 30 Mar 2017 05:25:13 +0000 Message-ID: <542CF652F8836A4AB8DBFAAD40ED192A4C5811AF@shsmsx102.ccr.corp.intel.com> References: In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTU5ZmMwNmUtZjdlOC00NDhkLTgxYjYtNWQ1ZDNmMzQ2ODg5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjdzSDhJRFpUZDZueFwvK25CSjBSZHFEVlBYckxyT0tPREZjSVA0ak5zMVkwPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [10.239.127.40] MIME-Version: 1.0 Subject: Re: Using Intel UDk debugger X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 05:25:26 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Arka, UDK Debugger tool supports your usage model. Please see the section "9.11 Debugging a standalone module loaded in a UEFI= shell" @ https://firmware.intel.com/sites/default/files/UDK_Debugger_Tool_= User_Manual_V1.11.pdf Thanks! Jeff -----Original Message----- From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Arka= Sharma Sent: Thursday, March 30, 2017 1:15 PM To: edk2-devel@lists.01.org Subject: [edk2] Using Intel UDk debugger Hi, I am sorry if it is not a right place to ask this. I have installed WinDbg = and Intel UDK debugger. I want to debug a driver and an application on an A= srock borad, but going through the UDK debugger user manual I realize that = SourceLevelDebugPkg has to be included in target firmware image. Now in thi= s case what option do I have to proceed with the debugging ? I am launching= my application from shell and in the shell post codes are disabled, the ap= plication code get stuck randomly. So far I was trying to debug with AsciiP= rints. Is there any way to use DEBUG macro to redirect debug messages from = UEFI driver as well as application to some serial port in this case ? Regards, Arka _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel