Re: [yocto] Post Generation of debug information

[Oliver]

In this special case the tool is Lauterbach's Trace32. 

If I understand properly each piece of output I would eventually need, I would 
need to modify its origin recipes to ensure they deploy the such files in 
DEPLOY_DIR_IMAGE/SOME_WHERE. There I could proceed in a similar way as the 
image_types classes.
Paths are the first motivation, but physical addresses, offsets configurations 
which might could only be fetched from grepping the code could be next. Ideally 
I would not like to modify others recipes.
In a more generic way, is there a way a recipe accesses variables of other 
recipes?


El Lunes 22 de febrero de 2016 19:46, Khem Raj  
escribió:
 

 On Mon, Feb 22, 2016 at 7:41 AM, Oliver  wrote:
> I have the need to generate some scripts for a debugger tool. As a first
> approach, these generated scripts could contain paths on where specific
> binary files are stored on the file system.
>
> Such purpose has been partially fulfilled with a recipe implementing the
> do_compile task to generate those files, assuming not implementing the
> deploying tasks, nothing gets integrated in the final image.
>
> Therefore the debugger tool could go to build/work/temp/…/myrecipe/…
> (WORKDIR of the recipe) as a startpoint for such scripts.
>
> 2 Questions:
>
> -          There would be a better solution for this task?
> -          The task has not been as successfully as expected. Ideally I
> would access variables of other recipes to know where they are their
> output/intermediate files. E.g. location of an elf file for u-boot. Is there
> any way around this?
>

There are ways implemented e.g. you can generate an image tarball in two pieces
1. binaries
2. Associated debug info and symbols

The untar both in same place.

Point your cross gdb to this location via setting appropriate sysroot
in .gdbinit
and that will be it.

However its not clear if thats what you are looking for. If you want to point to
components build directory instead of a full rootfs then you have to enhacne
the .gdbinit a bit more.

I am assuming that gdb is the debugging tool you are trying to use

> Regards
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>

  -- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Post Generation of debug information

[Khem Raj]

On Mon, Feb 22, 2016 at 7:41 AM, Oliver  wrote:
> I have the need to generate some scripts for a debugger tool. As a first
> approach, these generated scripts could contain paths on where specific
> binary files are stored on the file system.
>
> Such purpose has been partially fulfilled with a recipe implementing the
> do_compile task to generate those files, assuming not implementing the
> deploying tasks, nothing gets integrated in the final image.
>
> Therefore the debugger tool could go to build/work/temp/…/myrecipe/…
> (WORKDIR of the recipe) as a startpoint for such scripts.
>
> 2 Questions:
>
> -  There would be a better solution for this task?
> -  The task has not been as successfully as expected. Ideally I
> would access variables of other recipes to know where they are their
> output/intermediate files. E.g. location of an elf file for u-boot. Is there
> any way around this?
>

There are ways implemented e.g. you can generate an image tarball in two pieces
1. binaries
2. Associated debug info and symbols

The untar both in same place.

Point your cross gdb to this location via setting appropriate sysroot
in .gdbinit
and that will be it.

However its not clear if thats what you are looking for. If you want to point to
components build directory instead of a full rootfs then you have to enhacne
the .gdbinit a bit more.

I am assuming that gdb is the debugging tool you are trying to use

> Regards
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Post Generation of debug information

[Oliver]

I have the need to generate some scripts for a debuggertool. As a first 
approach, these generated scripts could contain paths on wherespecific binary 
files are stored on the file system. 


 
Such purpose has been partially fulfilled with a recipe implementingthe 
do_compile task to generate those files, assuming not implementing thedeploying 
tasks, nothing gets integrated in the final image. 


 
Therefore the debugger tool could go to build/work/temp/…/myrecipe/… (WORKDIR 
of the recipe) as a startpointfor such scripts.


 
2 Questions:


 
- There would be a better solution for this task?

- The task has not been as successfully asexpected. Ideally I would 
access variables of other recipes to know where theyare their 
output/intermediate files. E.g. location of an elf file for u-boot.Is there any 
way around this?


Regards-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto