Datasheet

Migrating Projects from SDT to ADS
4-16 Copyright © 1999-2001 ARM Limited. All rights reserved. ARM DUI 0064D
4.2.5 Calling constructors and destructors for top-level C++ objects
If you are using ARM C++ with SDT you must:
call constructors for top-level C++ library objects with an explicit call to
__cpp_initialise()
call destructors for top-level C++ library objects with an explicit call to
__cpp_finalise()
.
This is described in the SDT 2.51 Errata PDF, and in Application Note 74 Using ARM
C++ in Embedded Systems.
In ADS:
constructors for top-level C++ library objects are called by
__rt_lib_init()
.
destructors for top-level C++ library objects are called by
__rt_lib_shutdown()
.
You should not need to call __cpp_initialise() or __cpp_finalise() explicitly from your
application code if your application is being initialized in the normal way through
__main.
4.2.6 Updating debugger script files
Script files contain debugger commands that you might have recorded during a
debugging session, or added or changed with a text editor. You can submit a script file
instead of entering the commands individually if you want to repeat a particular
sequence of commands.
You can use the same commands with the debuggers armsd, ADW, and ADU. However,
AXD uses different commands. A script file that works with armsd, ADW, or ADU
usually requires updating before it works with AXD.
To update an armsd, ADW, or ADU script file to work with AXD you must understand
what each command in the file does and decide which of the following cases applies:
the script file still works in the same way with AXD
the script file requires some small change
the operation performed by the script file has to be done in a completely different
way with AXD.
An appendix to the AXD and armsd Debuggers Guide lists all the commands supported
by armsd, ADW, or ADU and by AXD, showing equivalences where they exist.
As an example, typical commands required for armsd, ADW, or ADU to debug an
embedded system (having code in ROM or flash memory) are: