core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_debug_rom.htm
author fturovic <frank.turovich@nokia.com>
Wed, 18 Aug 2010 13:43:53 -0500
changeset 1854 49624691da34
parent 1791 727385d8e2b3
child 2009 b622387629d6
permissions -rw-r--r--
BUG 11654 - pulled most of the TRACE32 refs except those in stop-mode (which needs rewriting yet)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="LASTUPDATED" content="06/17/05 11:09:43" />
<title>Debugging in ROM</title>
<link rel="StyleSheet" href="../../../book.css" type="text/css"/>
</head>
<body >
<h2>Debugging in ROM</h2>
<p>You will see symbolic information for other components when  you are debugging  in ROM using System TRK  if those components were built with symbolic information and the ROM Log file is specified. If a function in the stack crawl is in a ROM module and the IDE is able to find a file containing symbolic information for that module, the IDE will load it automatically and display function names. The IDE will also allow source level debugging and let you set breakpoints in this module. </p>
<p>Some issues to pay attention to  when debugging include: </p>
<ul>
  <li>In System TRK you must specify the ROM log file in the <a href="../../projects/launch/page_rom_log.htm">ROM Log</a> tab of the TRK  or Attach to Process launch configurations</li>
</ul>
<blockquote>
  <p class="note"><b>NOTE</b> You cannot debug ROM DLLs using Application TRK. </p>
</blockquote>
<div id="footer">Copyright &copy; 2010 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. <br>License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a></div>

</body>
</html>