[Tracing] Deciding the Yaml configuration for barectf input

[Vidushi Vashishth]

Hi!

Quick question. I tried to modify the printk trace generator to print the
output traces into a text file instead of the console. On running the
normal link and trace linker commands there are no compilation errors.
However when I run the application executable using GDB it says [Inferior 1
(process 42000) exited normally].

This is what I am doing to the code section of the rtld-print.ini's printk
generator:

static inline void rtld_pg_printk_entry(const char* func_name,
                                        void*       func_addr)
{
  FILE* fp = fopen("trace.txt", "a");
  fprintf (fp, ">>> %s (0x%08x)\n", func_name, func_addr);
  fclose(fp);
}

Is there something wrong with this approach?

On Thu, Jun 7, 2018 at 2:00 PM, Vidushi Vashishth <reachvidu at gmail.com>
wrote:

> Hi Sebastian.
>
>
>> I still have problems to see the big picture. Would it be possible to
>> implement both approaches using a simple example?
>
>
> I am working on the babeltrace approach and using the fileio test case to
> track entry and exit of malloc, calloc, realloc and free functions. I will
> have something ready very soon.  I will keep you updated.
>
> Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20180607/8ffffdf5/attachment-0002.html>