bitbake: utils.py: Try harder to extract good traceback information by querying the...
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 22 Aug 2012 19:01:12 +0000 (20:01 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Thu, 23 Aug 2012 08:22:42 +0000 (09:22 +0100)
commit6bcf8e32dbf14b66091c8cc1fbf163ea2a1cd69d
tree2b465c081c89820ff1cf0f26c9fca62d1f6bf6dd
parente019dafe8df203af70f7725438438bb4379c03b9
bitbake: utils.py: Try harder to extract good traceback information by querying the datastore

Currently as soon as execution passes outside the code fragment being
executed by better_exec, we don't get any good traceback information,
just a likely obscure reference to some function name which may
or may not be identifiable.

This patch adds code to query the datastore if present, allowing a more
meaningful back trace to be displayed in many cases.

[YOCTO #2981]

(Bitbake rev: 0edf8431f9ff52581afe0d3ef525c59909af02ba)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake/lib/bb/utils.py