Login

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

ARM Community: RealView Debugger: Error: E003A: Symbol not found - ARM Community

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

RealView Debugger: Error: E003A: Symbol not found Cannot set breakpoint in one particular file Rate Topic: ***-- 1 Votes

#1 User is offline   sergio1 

  • Member
  • Pip
  • Group: Members
  • Posts: 1
  • Joined: 12-April 12

Posted 12 April 2012 - 02:47 PM

I am not able to set breakpoints in any function in one particular in my source code project.

I get this error when I attempt to set the break point:

Error: E003A: Symbol not found.

At one point I was able to set break points



To fix the issue I tried the following:

1. Cleaned out the entire build manually, and rebuilt the debug symbols.

2. Made sure I load the correct .axf file

3. I can see my code is being executed. For example I put/change debug prints to make sure it’s the right code and is being called by other modules. So it is included in the build.


4. Asked coworkers to do the same, some experience the problem and others don’t. One co-worker, cleaned out his build, like me and it started working again.


5. I can set breakpoints in other files in the same library/folder and in other libraries in my project



I am using the RVDEBUG version 4.1.1 build 25.

My question:

Is there something I can do to via the debugger that I can clean up or restore? Is there some stale project auto generated file that I can remove?


0

#2 User is offline   isogen74 

  • Super Contributor
  • PipPipPipPip
  • Group: Members
  • Posts: 1098
  • Joined: 20-March 07

Posted 13 April 2012 - 07:28 AM

Try setting -O0 and force disable inlining. Inlined symbols sometimes have this problem.
When optimizing software, consider that the quickest code to run is the bit you removed from the call path.
1

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic