Check that breakpoints are inherited correctly across switches

Registered by Naresh Kamboju

Define and implement tests: Check that breakpoints are inherited correctly across switches.
Note: very new upstream gdb may also be needed for H/W breakpoints to work properly.
ARM may already have some tests we may reuse those.

Blueprint information

Status:
Complete
Approver:
Alexander Sack
Priority:
High
Drafter:
Naresh Kamboju
Direction:
Needs approval
Assignee:
Naresh Kamboju
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
milestone icon 2013.05
Started by
Naresh Kamboju
Completed by
Milosz Wasilewski

Related branches

Sprints

Whiteboard

[dave-martin-arm] commented:
debug migration is not likely to get implemented this year, this
may be lower priority. We will disable hardware-assisted debug and
use software-only debug, which should be mature -- we should have some
simple tests to sanity check that we can debug across a switch, but
software debug is mature so we shouldn't need to test aggressively.

I had something like this in mind:

        static void handler(int n) { }

        void finish(void) { }

        main()
        {
                signal(SIGUSR1, handler);
                pause();
                finish();
        }

Then:
        start the program in gdb

        set a breakpoint on finish

        run

        switch to the other cluster

        send SIGUSR1 to the debugged program

        check that gdb stops on the previously set breakpoint

[nkambo 15 Feb 2013]
Android do not have gdb command for testing debug support.
Android has gdbserver command, which is used for remote debug purpose.
I have started testing debug support by using remote gdb. which is under progress.

[nkambo 13 March 2013]
this test has been executed manually on big.LITTLE IKS kernel image.
since Android support only remote debugging, we could not automate this test execution. so which is not a part of big.LITTLE IKS core test suite now. which needs to be addressed in this March cycle on way forward.

[asac 3 April 2013]
moved to 2013.04; it became clear that automation is not as trivial as it seemed because android has no native gdb that could be used for automation on the test device installed.

[nkambo April 25 2013]
I am testing this test case manually.
no more automation required here.

[mwasilew 30 Apr 2013]
Closing blueprint. Only manual test case will be executed.

Meta:
Headline: Check that breakpoints are inherited correctly across switches
Acceptance: Debug support test procedure using gdb or gdbsever commands should be available.
Roadmap id: big.LITTLE IKS

Deliverable :
Testing break points test case by using manual procedure.

(?)

Work Items

Work items:
Develop test cases for gdb: DONE
connect TC2 with remote gdb and test : DONE
Integrate test cases in core test suite: POSTPONED
Test these test cases on Android builds: DONE

This blueprint contains Public information 
Everyone can see this information.