• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 776 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

Compiler/AM3352: program behaviors weird

Compiler/AM3352: Disassembly line doesn't match with source file line

Andy Lin94
Expert 1390 points
Part Number: AM3352


Tool/software: TI C/C++ Compiler

Here are my working steps

1. Clean Project

2. Build Project

3. CPU Reset(HW)

4. CPU Reset(SW)

5. Load Program(.out file is checked as newest one)

6. Disassembly line doesn't match with source file line

And this is my project setting

  • 0
    TI__Guru**** 173310 points

    The source line correlation here appears ok to me, however please note that, in general, turning on optimization can impact the debug experience as mentioned in your other post.  Hope this clarifies or explains the debugger behavior.

  • 0 in reply to AartiG
    Expert 1390 points
    Hi. What do you mean by source line correlation appears ok to you?

    Did you mean that It's fine for the different entry point(GPIO_Init() for disassembly and left parenthesis for main source) as long as line numbers are matched?
  • 0 in reply to Andy Lin94
    TI__Guru**** 173310 points

    Andy Lin94 said:
    Did you mean that It's fine for the different entry point(GPIO_Init() for disassembly and left parenthesis for main source) as long as line numbers are matched?

    I was referring to the line numbers matching up between the source view and disassembly view. Basically, the call to GPIO_init() is at line 22 of the source file, and the disassembly view shows the same line number.

    I realize now that you are talking about the execution line pointed to by the arrow in the source view vs disassembly view. Is that correct? What happens when you step through the code - does it also jump around in the disassembly view?

  • 0 in reply to AartiG
    Expert 1390 points

    Hi, here is my new info.

    I restored the program to previous version from SVN which is working well and added new feature step by step.
    Then I noticed a bug where memset is enormously beyond the scope.
    I fixed this bug, and this problem is also disappear, too.

    I'm suspecting that maybe memset was stepping on instruction scope of RAM and affecting program behavior.
    Is that possible? Or how do I know it?

    Thanks!

  • 0 in reply to Andy Lin94
    TI__Guru**** 173310 points
    Andy,

    Glad to hear that the disassembly issue is resolved. However, with the information provided, I can't tell for certain whether it was related to the memset or not. I would just recommend keeping an eye on it and looking for code changes or triggers if the issue does appear again at a later time. Thanks for providing an update.