P. 1
Delphi - Reviewer Guide

Delphi - Reviewer Guide

|Views: 380|Likes:
Published by Luciano Marwell
Delphi, Guia do Desenvolvedor, Programação
Delphi, Guia do Desenvolvedor, Programação

More info:

Published by: Luciano Marwell on Feb 11, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

11/05/2012

pdf

text

original

Delphi 2005 doesn't just have a world-class debugger ⎯ it has two. One of these is for your

.NET applications that you have compiled to IL, and the other is for your Win32 applications

that you've compiled to machine language.

Delphi 2005 selects which of these debuggers to use based on the type of compiler that

created your executable. For example, if you are debugging an ASP.NET Web application, a

Windows Forms application, or a VCL for .NET application, Delphi 2005 uses the Borland

.NET Debugger. By comparison, if you are debugging a VCL client/server application, a

COM (component object model) server, or a traditional Win32 DLL, Delphi 2005 uses the

Borland Win32 Debugger.

Just as Borland provides you with a consistent set of features when it comes to compiling,

Borland's debuggers do a remarkable job of giving you a rich, dependable, and consistent set

of tools for debugging your applications, whether you are compiling for .NET, Win32, or

both. For example, each of Delphi 2005's debuggers permits you to set breakpoints, view the

call stack, change the values of variables and objects, access local variable values, switch

between your application's current threads, view CPU (central processor unit) data, examine

the event log, as well as access the list of loaded modules. You can even use these debuggers

to attach to existing processes, giving you insight into how they are functioning.

Page 65

Borland Delphi 2005 – Reviewers Guide

While the features offered by these two debuggers are consistent, they are not identical.

Specifically, each debugger provides you with options appropriate for the associated

executable.

For example, with Win32 applications you can create Data breakpoints, breakpoints that

trigger when the data stored in a particular memory address changes. Data breakpoints don't

make sense in the .NET world, since the physical address in which data is stored cannot be

predicted.

On the other hand, the CPU window displayed by the .NET debugger can include the IL

(intermediate language) the .NET compiler emitted. Win32 compilers don't generate IL, so

this feature does not apply to Win32 executables.

The following sections provide you with information about new features that appear in the

debuggers for Delphi 2005.

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->