diff options
| author | Khem Raj <raj.khem@gmail.com> | 2024-02-03 22:00:20 -0800 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-02-09 13:45:02 +0000 |
| commit | e1f691072737978a1ddbdabeac529ed005508977 (patch) | |
| tree | ee81744fbd2329af333814bd084b13e5898ea3c5 /meta/conf/machine/include | |
| parent | 71ac318a830b37f55cbd63794c55c6adc1904f1f (diff) | |
| download | poky-e1f691072737978a1ddbdabeac529ed005508977.tar.gz | |
gcc-runtime: Move gdb pretty printer file to auto-load location
When debugging a C++ program on target using libcstdc++, gdb does not
find the pretty printer python support, this is because the init file is
installed into /usr/lib which is excluded from gdb's default list of
directories to load config's from, where as defaults to load from
datadir is still on, it therefore does not load this file
warning: File "/usr/lib/libstdc++.so.6.0.33-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
This leaves the libstdc++ pretty-printers disabled even though added via
IMAGE_INSTALL += "gcc-runtime-dbg"
Comment on adding missing runtime dependency on datetime python module for the pretty
printer to work/load successfully.
Once the pretty-printer gdb file is moved out of libdir, it may become
empty therefore delete it if its empty.
(From OE-Core rev: d24e16d192f21aa68b5274496efaba1d913f37c2)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf/machine/include')
0 files changed, 0 insertions, 0 deletions