Re: Oddity with address recorded for gcc instrumentation on ARM

2020-12-21 Thread Chris Johns
On 19/12/20 7:56 am, Sebastian Huber wrote: > If you build the RTEMS tools with the LLVM development package you get the > function name and line information in the trace. Is there a wrote up or walk through on how to do this? Thanks Chris ___ devel

Re: Oddity with address recorded for gcc instrumentation on ARM

2020-12-21 Thread Peter Dufault
> On Dec 18, 2020, at 17:52 , Joel Sherrill wrote: > > > Can someone explain this? > These are link register values. The least significant bit determines if > a bx instruction continues in ARM or Thumb mode. > > I guess I've never had to look that close. Thanks Sebastian. > It had me

Re: Oddity with address recorded for gcc instrumentation on ARM

2020-12-18 Thread Joel Sherrill
On Fri, Dec 18, 2020, 2:55 PM Sebastian Huber < sebastian.hu...@embedded-brains.de> wrote: > On 18/12/2020 20:51, Ryan Long wrote: > > > Can someone explain this? > These are link register values. The least significant bit determines if > a bx instruction continues in ARM or Thumb mode. > I

Re: Oddity with address recorded for gcc instrumentation on ARM

2020-12-18 Thread Sebastian Huber
On 18/12/2020 20:51, Ryan Long wrote: Timestamp     Channel CPU   Event type  Contents TID Prio        PID    Source 18:00:06.483 017 719 stream_0 0  FUNCTION_ENTRY   code=0x104ec7 167837716

Re: Oddity with address recorded for gcc instrumentation on ARM

2020-12-18 Thread Sebastian Huber
On 18/12/2020 20:51, Ryan Long wrote: Can someone explain this? These are link register values. The least significant bit determines if a bx instruction continues in ARM or Thumb mode. -- embedded brains GmbH Herr Sebastian HUBER Dornierstr. 4 82178 Puchheim Germany email:

Oddity with address recorded for gcc instrumentation on ARM

2020-12-18 Thread Ryan Long
Hi, We turned on gcc instrumentation with a test function, and got the following records. Timestamp Channel CPU Event type Contents TID PrioPID Source 18:00:06.483 017 719