OpenArbor 12.1.0 BreakAtStartup Testing Report

From DDCIDeos
Jump to navigationJump to search

This report documents the manual testing done while working on DDCI_PCR:5010
OA was modified to have the .gdbinit generated file contain:
b _start for ppc and 80x86 bsps.
b _init for ppc and 80x86 bsps, if an rtems application is integrated.

Following are the set of steps needed to create an automated test for the 'breakAtStartup' functionality.

Test Description

In the application project, set breakAtStartup to 'yes' (or 'true')

  For hello-world, modify hello-world.pd.xml

  For buffer-semaphore-configuration, modify buffer_config.653.xml

  For rtems-cpu-usage, modify rtems-cpu-usage.pd.xml

Integrate application project with bsp
if testing QEMU target - Launch emulator
Ensure target is pinging
Update Target Load (set to normal mode & honor debug services & force cold start)
Enable Status Monitor
Launch a debugging session on the exe with gdb
Verify initial breakpoint location is as expected.
Resume (Go)
Verify application is running (not suspended)
Remove all breakpoints
Terminated debugging session
Undo edits to the xml files above

Testing Notes

Status DDS App Type Project Name OS Target .gdbinit Content Screenshot Comments
Pass DDS-sales-deos-kismet-202318 RMA hello-world Windows QEMU-ARM (qemu-arm) Media:rma-hello-world-arm-breakAtStartup.png The initial bp is encountered as expected, and after 1 go, the application is running.
Pass DDS-sales-deos-kismet-202318 Rtems rtems-cpu-usage Windows QEMU-ARM (qemu-arm) Media:rtems-rtems-cpu-usage-arm-breakAtStartup.png The initial bp is encountered as expected, and after 1 go, the application is running.
Pass DDS-sales-deos-kismet-202318 653 buffer-semaphore Windows QEMU-ARM (qemu-arm) Media:653-buffer-semaphore-arm-breakAtStartup.png The initial bp is encountered as expected, and after 1 go, the application is running.
Pass DDS-sales-deos-kismet-202318 RMA hello-world Windows QEMU-PPC (qemu-ppc) b _start Media:rma-hello-world-ppc-breakAtStartup3.png The initial bp is encountered as expected, and after 1 go, the application is running.
Fail DDS-sales-deos-kismet-202318 Rtems rtems-cpu-usage Windows QEMU-PPC (qemu-ppc) b _start
b _init 		Media:rtems-rtems-cpu-usage-ppc-breakAtStartup.png The initial bp of debuggerSuspend() is unexpected, and it takes 3 Go's to get the application running.
After the first go, the debugging session is suspended at Image:loadFile() at image.cpp:245
After the second go, the debugging session is supended at _init() at rtems_crti.S:65
After the 3rd go, the application is running.
Pass DDS-sales-deos-kismet-202318 653 buffer-semaphore Windows QEMU-PPC (qemu-ppc) b _start Media:653-buffer-semaphore-ppc-breakAtStartup2.png The initial bp is encountered as expected, and after 1 go, the application is running.
Pass DDS-durants-deos-jupiter-20231116 RMA hello-world Windows DeosCOMe-cTL6-1 (come-clt6) b _start Media:rma-hello-world-x86-breakAtStartup.png The initial bp is encountered as expected, and after 1 go, the application is running.
Fail DDS-durants-deos-jupiter-20231116 Rtems rtems-cpu-usage Windows DeosCOMe-cTL6-1 (come-clt6) b _start
b _init 		Media:rtems-rtems-cpu-usage-x86-buildErrors.txt Unable to test due to: /bin/bash: i386-rtems5-gcc: command not found
Pass DDS-durants-deos-jupiter-20231116 653 buffer-semaphore Windows DeosCOMe-cTL6-1 (come-clt6) b _start Media:653-buffer-semaphore-x86-breakAtStartup.png The initial bp is encountered as expected, and after 1 go, the application is running.
Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=OpenArbor_12.1.0_BreakAtStartup_Testing_Report&oldid=59359"