TS 68 CNDgdblite

GDB Test Specification

Author: Alexander Pepin
Version: 1.0
Lastupdate: 9.9.2009
Introduction:

Contents 1 GDB Test Specification 1.1 Test suite: Actions 1.2 Test suite: Views 1.3 Test suite: Breakpoints 1.4 Test suite: Multi-Threaded Debugging 1.5 Test suite: Attach To Process 1.6 Test suite: Known Issues (Regression tests)

Test suite: Actions

• Start

1. • create a sample application
   • set a breakpoint in the main function
   • start debugger

1. • start via toolbar button
   • start via main menu
   • start via project context menu

1. • verify that debugger started correctly

• Step Into Project

1. • create a sample application
   • do step into project

1. • step into via project context menu
   • step into via main menu

1. • verify that debugger started correctly

• Step Over

1. • create a sample application
   • do step into project
   • do step over

1. • step over via main menu
   • step over via toolbar
   • step over via shortcut

1. • verify that debugger stepped over correctly

• Step Into

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function

1. • step into via main menu
   • step into via toolbar
   • step into via shortcut

1. • verify that debugger stepped into function correctly
   • do step into system function

1. • step into via main menu
   • step into via toolbar
   • step into via shortcut

1. • verify that debugger stepped into function correctly

• Step Out

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • do step out function

1. • step out via main menu
   • step out via toolbar
   • step out via shortcut

1. • verify that debugger stepped out function correctly
   • do step into system function
   • do step out system function

1. • step out via main menu
   • step out via toolbar
   • step out via shortcut

1. • verify that debugger stepped out function correctly
   • do step out 'main' function

1. • step out via main menu
   • step out via toolbar
   • step out via shortcut

1. • verify that debugger stepped out main function correctly

• Continue

1. • create a sample application
   • set a breakpoint in the main function
   • start debugger
   • when debugger stops at BP do continue

1. • continue out via main menu
   • continue out via toolbar
   • continue out via shortcut

1. • verify that debugger continued execution correctly

• Pause

1. • create an application with an endless loop
   • start debugger
   • when debugger starts do pause

1. • pause out via main menu
   • pause out via toolbar
   • pause out via shortcut

1. • verify that debugger paused execution correctly

• Finish

1. • create a sample application
   • do step into project
   • do finish

1. • finish out via main menu
   • finish out via toolbar
   • finish out via shortcut

1. • verify that debugger finished execution correctly

• Make Current

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • open Call Stack view
   • select any stackframe and make it current
   • verify that Local Variables view and Watches were updated accordingly

• Pop To Here

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • open Call Stack view
   • select caller stackframe and do pop to here
   • verify that debugger stops in caller function

• Pop Topmost Call

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • open Call Stack view
   • open Debug menu Stack section and do pop topmost call
   • verify that debugger stops in topmost caller function

• Make Caller Current

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • open Call Stack view
   • open Debug menu Stack section and make caller current
   • verify that Local Variables view and Watches were updated accordingly

• Make Callee Current

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • do step into function
   • open Call Stack view
   • open Debug menu Stack section and make caller current
   • open Debug menu Stack section and make callee current
   • verify that Local Variables view and Watches were updated accordingly

Test suite: Views

• check views, open, close etc.

1. • create a sample application
   • do step into project
   • check Local Variables view, open, close, change visible columns etc.
   • check Watches view, open, close, change visible columns etc.
   • check Call Stack view, open, close, change visible columns etc.
   • check Sessions view, open, close, change visible columns etc.
   • check Breakpoints view, open, close, change visible columns etc.
   • check Threads view, open, close, change visible columns etc.
   • check Registers view, open, close, change visible columns etc.
   • check Memory view, open, close, change visible columns etc.

• Local Variables

1. • create a sample or some specific application
   • do step into project
   • check LV on sample projects
   • check LV in function
   • check numbers (short, int, long, float, double)
   • check char
   • check pointers
   • check arrays
   • check unions
   • check classes
   • check structures
   • modify values
   • check that values are updated accordingly

• Watches

1. • create a sample or some specific application
   • do step into project
   • create a new watch
   • customize watch
   • delete watch
   • watch for function
   • modify values
   • check that values are updated accordingly

• Call Stack

1. • create a sample application with functions (e.g. Quote)
   • do step into project
   • call stack representation
   • see call stack actions

• Breakpoints

1. • create a sample or some specific application
   • set several breakpoint
   • do step into project
   • open Breakpoints view
   • check breakpoint representation
   • check Go To Source option
   • diasable BP
   • check that debugger ignore disabled BP
   • diasable all BPs
   • check that debugger ignore disabled BPs
   • enable BP
   • check that debugger stops at BP
   • enable all BPs
   • check that debugger stops at BPs
   • customize BP (see Breakpoints section)

1. • line number
   • condition
   • event counter
   • action
   • print text

1. • check that changed options has effect
   • delete BP
   • check that debugger does not stop at BP
   • delete all BPs
   • check that debugger does not stop at any BPs

• Sessions

1. • create two or more sample or specific applications
   • set several breakpoint in these applications
   • do step into project or start debugger for each application
   • open Sessions view
   • check sessions representation in Sessions view
   • switch between sessions and check that Local Variables and Watches are changed accordingly

• Threads

1. • create a multithreaded application
   • do step into project and do steps needed to create new threads
   • open Threads view
   • check threads representation
   • switch between threads and check that Local Variables and Watches are changed accordingly

• Memory

1. • create an application which modifies memory
   • do step into project
   • open Memory view and check memory content at the specific address
   • do some steps and check that memory content is changed accordingly

• Disassembly

1. • create a sample application
   • do step into project
   • open Disassembly view and check disassembled source code
   • do some steps and check that cursor moves accordingly

• Registers

1. • create a sample application
   • do step into project
   • open Registers view and check its content
   • do some steps and check that content is changed accordingly

• Debugger Console

1. • create a sample application
   • do step into project
   • open Debugger Console
   • do some steps and check console output

• Output

1. • create a sample application that needs input and produces output (e.g. Quote)
   • set Run/Console Type property to Output Window
   • do step into project
   • do some steps and check that needed data can be entered and check output

• Terminal wnidow

1. • create a sample application that needs input and produces output (e.g. Quote)
   • set Run/Console Type property to Default
   • do step into project
   • check that a new terminal window appears
   • do some steps and check that needed data can be entered and check output

Test suite: Breakpoints

• Function BP

1. • create a sample application containing function calls (e.g. Quote)
   • call Debug/New Breakpoint from the main menu
   • set a breakpoint type to Function then enter function name and press OK
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Line BP

1. • create a sample application
   • call Debug/New Breakpoint from the main menu
   • set a breakpoint type to Line then enter a desirable line number and press OK
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Adress BP

1. • create a sample application
   • do step into project
   • open Disassembly view and remember an address where a breakpoint can be set
   • call Debug/New Breakpoint from the main menu
   • set a breakpoint type to Address then enter a desirable address and press OK
   • continue debugging and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Toggle BP

1. • create a sample application
   • click on the gutter next to line in the editor where a breakpoint should be set
   • check that the breakpoint is created and a breakpoint annotation is added to the source file in the editor
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Customize BP

1. • customize (change function/line)
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Conditional BP

1. • check condition
   • check count exceeds
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

• Actions for BP

1. • check suspend
   • check Thread ID
   • check Print Text
   • start debugger and check that created breakpoint does work
   • check that the breakpoint is displayed correctly in Breakpoints view

Test suite: Multi-Threaded Debugging

• Breakpoints

1. • create a multithreaded application
   • check global BP
   • check BP for each thread (see breakpoint customize section)

• LV/Watches

1. • create a multithreaded application
   • check LV/Watches for thread (see Local Variables and Watches)

Test suite: Attach To Process

• Attach to process

1. • create a managed application
   • run the application (in the IDE or from outside)
   • call attach to process dialog
   • find the process and attach to it
   • debug attached process (check breakpoints, views, etc. )
   • repeat the same steps for a makefile based application

• Attach to remote process

1. • create a managed remote application
   • run the application in the IDE
   • call attach to process dialog
   • select an appropriate remote host
   • select an appropriate project name
   • find the process and attach to it
   • debug attached process (check breakpoints, views, etc. )
   • repeat the same steps for a makefile based application

• Attach to GDB server

1. • create a managed application (local or remote)
   • run the application (in the IDE or from outside)
   • call attach to process dialog
   • select "Gdb Server" in the Debugger combobox
   • set an appropriate hostname and port
   • select an appropriate project name
   • debug attached process (check breakpoints, views, etc. )
   • repeat the same steps for a makefile based application

• Simple attach to the running process

1. • create a managed application (local or remote)
   • run the application in the IDE
   • press "Attach Debugger" button in the "Build,Run" output tab
   • debug attached process (check breakpoints, views, etc. )
   • repeat the same steps for a makefile based application

Test suite: Known Issues (Regression tests)

• 112359 All Incorrect type info for std::string

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112359

• 112618 PC It is impossible to change array member values using Local Variables View

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112618

• 112620 PC It is impossible to assign values for enum

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112620

• 112621 PC impossible to assign bool value in Local Variables View

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112621

• 112657 All Incorrectly displayed names/values in LV view for unions

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112657

• 112660 All Local variable and Watch nodes collapse after every step

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112660

• 112664 PC structs displayed incorrectly in Local Variables view

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112664

• 112667 PC Local Variables view should show fields defined in super class

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112667

• 112674 All Array and union members in a class are not displayed in LV

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112674

• 112680 All Complex node in the class can not be expanded after stepping

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112680

• 112682 All Union members can not be changed via Local Variables

1. • http://www.netbeans.org/issues/show_bug.cgi?id=112682

• 113688 All Modifying union value in LV doesn't update other fields

1. • http://www.netbeans.org/issues/show_bug.cgi?id=113688

• 114188 All Wrong multi dim array representation in LV

1. • http://www.netbeans.org/issues/show_bug.cgi?id=114188

• 114191 All Values changed in the LV and WV don't visually persist

1. • http://www.netbeans.org/issues/show_bug.cgi?id=114191

• 115346 All StringIndexOutOfBoundsException in watch with empty string

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115346

• 115378 All IDE fails while watching function with breakpoint

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115378

• 115380 All Watch still shows old values after changing the expression

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115380

• 115425 All Type field in watches joints after changing watched expression

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115425

• 115427 All Two watches show different values for the same variables

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115427

• 115464 All Debug process fails if watch expression fails

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115464

• 115728 All Debugger hangs if code contains a class without members

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115728

• 115735 All LV does not show base classes members of the class

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115735

• 115853 All Unnamed union is not shown

1. • http://www.netbeans.org/issues/show_bug.cgi?id=115853

• 116003 All Class members are not shown in LV if it's referenced by pointer

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116003

• 116007 All Empty function name in customize BP dialog

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116007

• 116031 All Type of class in watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116031

• 116234 All Sleep in watched function makes step start more sessions

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116234

• 116303 All LV and Watches do not show char array elements

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116303

• 116305 All Array elements are not updated in Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116305

• 116480 PC Invalid watches hang debug session

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116480

• 116539 All LV and Watches do not dereference pointers

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116539

• 116683 All Function in watch is not evaluated

1. • http://www.netbeans.org/issues/show_bug.cgi?id=116683

• 118003 All Can not change value referenced by pointer if the pointer is a class member

1. • http://www.netbeans.org/issues/show_bug.cgi?id=118003

• 118009 All LV and Watches should update after changing any value

1. • http://www.netbeans.org/issues/show_bug.cgi?id=118009

• 118012 All std::string is not expandable in LV and Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=118012

• 121988 All Variables in Watches get collapsed

1. • http://www.netbeans.org/issues/show_bug.cgi?id=121988

• 122996 All Wrong names of array elements in Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=122996

• 122997 All Wrong order of array elements in Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=122997

• 125587 All LV doesn't handle nested/hidden variables

1. • http://www.netbeans.org/issues/show_bug.cgi?id=125587

• 126196 All Variable in LV gets collapsed after each step

1. • http://www.netbeans.org/issues/show_bug.cgi?id=126196

• 126197 All Pointers are not expandable in LV and Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=126197

• 126199 All Class members in Watches are not updated

1. • http://www.netbeans.org/issues/show_bug.cgi?id=126199

• 126639 All LV and Watches do not show std::string if it's a class member

1. • http://www.netbeans.org/issues/show_bug.cgi?id=126639

• 128498 All int variable has a child element in Watches

1. • http://www.netbeans.org/issues/show_bug.cgi?id=128498

• 128721 Sun Customized breakpoints does not work

1. • http://www.netbeans.org/issues/show_bug.cgi?id=128721

• 128752 All Huge number of array elements on the final step over

1. • http://www.netbeans.org/issues/show_bug.cgi?id=128752

• This page was last modified on 5 November 2009, at 17:36.
• This page has been accessed 15 times.