apullin Beginner

  • Member since Mar 31st 2010
Last Activity

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Will the output from the Ozone code profile listing for the "load" metric be valid for functions that are moved to a run-from-RAM section via a gcc attribute? e.g. __attribute__ ((section (".fast"))) , with the .fast section located in the RAM segment by…
  • apullin -

    Replied to the thread Reported location of variable in watch changes.

    Post
    Adding that watch does not cause a crash in 2.56w . I have had a lot of other problems with versions > 2.60 , hangs and crashes when resetting and reflashing. Looking forward to things getting stabilized.
  • apullin -

    Replied to the thread Reported location of variable in watch changes.

    Post
    One follow-on here: If I try to enter in a watch of *(uint32_t*)0x200221D8 , Ozone crashes immediately. Version 2.60e running on OSX 10.14 Mojave.
  • apullin -

    Replied to the thread Reported location of variable in watch changes.

    Post
    Alright, for a little more exposition, the error can be captured in a simple printf of the address before and after the function call. e.g.: C Source Code (1 line) Looking at the disassembly, this compiles to: Source Code (4 lines)Where 0x080B0070 is…
  • apullin -

    Replied to the thread Reported location of variable in watch changes.

    Post
    I can't profile the elf, since it would contain our proprietary source. Maybe if we put an NDA in place? But then you would need very specific hardware for the ELF to even run. This issue also happens when using gdbserver + eclipse + GNU Arm Eclipse…
  • apullin -

    Posted the thread Reported location of variable in watch changes.

    Thread
    I am debugging a project with Ozone, and I am seeing something that I do not understand the cause of. It may have a clear cause ... or it may be an Ozone bug. I'm unsure. In the code that I debugging, I am setting a watch on a stack variable (a struct),…