[U-Boot] [PATCH 4/4] WIP: travis: Add qemu-x86_64 target for test.py testing

Bin Meng bmeng.cn at gmail.com
Fri Oct 12 01:45:57 UTC 2018


Hi Heinrich,

On Fri, Oct 12, 2018 at 6:10 AM Heinrich Schuchardt <xypron.glpk at gmx.de> wrote:
>
> On 10/11/2018 03:57 AM, Bin Meng wrote:
> > Hi Heinrich,
> >
> > On Thu, Oct 11, 2018 at 9:48 AM Bin Meng <bmeng.cn at gmail.com> wrote:
> >>
> >> Add qemu-x86_64 to the list of targets we use for test.py runs.
> >>
> >> Signed-off-by: Bin Meng <bmeng.cn at gmail.com>
> >>
> >> ---
> >> testp.py testing is currently failing at 'bootefi selftest'.
> >>
> >
> > Can you try this series for the 'bootefi selftest' testing?
>
> I am clueless why the EFI subsystems is failing completely on
> qemu-x86_64_defconfig.
>
> Any printf() or puts() statement I put into
> lib/efi_loader/efi_boottime.c leads to no output at all.
>
> I connected gdb with
>
> gdb u-boot -ex 'target remote localhost:1234'
> add-symbol-file u-boot <relocaddr>
>
> But the debugger did not stop at breakpoints.

I encountered exactly the same issue that breakpoint is not hit when
debugging this endless loop issue. And I finally figured it out:

The symbol table should not be loaded to <relocaddr>, instead it needs
to be loaded to <relocaddr + .text - .text.start>.

The .text.start was introduced in commit
7e21fbca26d18327cf7cabaad08df276a06a07d8 "efi_loader: Rename sections
to allow for implicit data", and its commit message mentioned: [agraf:
Fix x86_64 breakage], although I was not sure what x86_64 breakage was
fixed.

Please have a try.

Regards,
Bin


More information about the U-Boot mailing list