[OE-core] gdb failure on simplest hello world program -- oe-selftest

richard.purdie at linuxfoundation.org richard.purdie at linuxfoundation.org
Wed Dec 26 11:06:46 UTC 2018


On Wed, 2018-12-26 at 10:09 +0800, ChenQi wrote:
> Hi All,
> 
> 'oe-selftest -r package.PackageTests.test_gdb_hardlink_debug' fails.
> I did the tests on both my Fedora27 and ubuntu16.04 servers. They both 
> failed.
> I can also reproduce this issue manually.
> 
> I did some investigation. No clue how to fix this it. So I want to seek 
> help from community.
> 
> Below is some output from oe-selftest.
> [snip]
> 2018-12-26 09:27:58,440 - oe-selftest - INFO - test_gdb_hardlink_debug 
> (package.PackageTests)
> 2018-12-26 09:37:55,333 - oe-selftest - INFO - gdbtest /usr/bin/hello1
> 2018-12-26 09:37:59,904 - oe-selftest - ERROR - GDB result:
> 1: Reading symbols from /usr/bin/hello1...Reading symbols from 
> /usr/bin/.debug/hello4...done.
> done.
> (gdb) Breakpoint 1 at 0x1060: file /usr/include/bits/stdio2.h, line 107.
> (gdb) Starting program: /usr/bin/hello1
> 
> Breakpoint 1, main () at /usr/include/bits/stdio2.h:107
> 107    /usr/include/bits/stdio2.h: No such file or directory.
> (gdb) Continuing.
> Hello World!
> [Inferior 1 (process 312) exited normally]
> (gdb)
> 2018-12-26 09:38:00,907 - oe-selftest - INFO -  ... FAIL
> [snip]
> 
> The hello world problem is as follows.
> $ cat 
> meta-selftest/recipes-test/selftest-hardlink/selftest-hardlink/hello.c
> #include <stdio.h>
> 
> int main() {
>      printf("Hello World!\n");
> }
> 
> Some extra information:
> 1. Remove '-O2' or '-D_FORTIFY_SOURCE=2', and it works correctly.
> 2. Adding some system call like daemon(0,0) before printf also works.
> 3. Reverting poky repo to 1c048479af7cc98e30f9a33d1f3bef03711544aa, 
> which adds this selftest case, does not work. It still fails.
> 4. Hongxu confirms that things work on his host.
> 5. I also don't see failure about this test case on yocto's autobuilder.
> 
> Could somebody help to provide some suggestions?

This is strange and there must be some difference between your
configuration and what what we test on the autobuilder or on Hongxu's
setup.

Which DISTRO and MACHINE are you using?

I think the key to resolving this is will be to understanding how to
reproduce it...

I think its worth investigating and figuring out...

Cheers,

Richard





More information about the Openembedded-core mailing list