partha sarathi swain [mailto:[email protected]] wrote:
]Jeff,
]I tried the same before, but when we put the break point in some application
Source file ](Suppose in helloworld.c) and attach to VS2010 it will land at
entry point of the ]application i.e ProcessModuleEntryPointList (NOT INSIDE
THE SOURCE FILE). Is there any other ]way ?
For the best source level debugging support you must use a NOOPT (no
optimization) build. The EDK2 DEBUG and RELEASE builds are both fully
optimized, resulting in inlined functions and register variables. The Microsoft
debugger doesn't handle either of these well.
NOOPT builds are not enabled by default in EDK2 code. But enabling the NOOPT
build is easy. Just make this change to your .dsc file:
BUILD_TARGETS = DEBUG|RELEASE
to BUILD_TARGETS = DEBUG|RELEASE|NOOPT
Then change your build.exe command line to use '-b NOOPT' in place of '-b
DEBUG'.
Thanks,
Scott
]Thanks & Regards
]
]Partha Sarathi Swain
]ASD Dept.
]LSI India Research and Development Center,
]Bangalore-560103.
]
]-----------------------------------------------------------------------------------------------]---------------------------------------------------
]"The earth is round and the place which may seem like the end may also be the
beginning"
]-----------------------------------------------------------------------------------------------]---------------------------------------------------
]
]On Wed, Sep 24, 2014 at 2:28 PM, Fan, Jeff <[email protected]> wrote:
]Debugging NT32 emulator does not need Intel UDK Debugger and
SourceLevelDebugPkg.
]
]Attach SecMain.exe and put one CpuBreakpoint () in your code and use Visual
Studio to do source ]debugging.
]
]From: partha sarathi swain [mailto:[email protected]]
]Sent: Wednesday, September 24, 2014 4:21 PM
]To: [email protected]
]Subject: [edk2] Debugging a application running on NT32 Emulator using Intel
EDK debugger tool
]
]Hi all,
]I have developed an application using UDK2014 and tested it on NT32 emulator.
]Now i put a software interrupt so that i can attach the process (SecMain.exe)
to a debugger.
]I started Intel EDk Debugger tool and kept the channel as "PIPE" like one
below
]
][Debug Port]
]Channel = PIPE
]Port = PipeName
]
]But i am not able to debug the source. Pipename is not listed in the process
handles.
]
]Note: i have included the "SourcelevelDebugPkg" in Nt32Pkg.dsc.
]
]Could you please suggested me a way to debug the application running in NT32
emulator.
]
]Thanks & Regards
]
]Partha Sarathi Swain
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/edk2-devel
