1 The gdb shows what line of code caused the program to core dump.

2 A bad comment restates what a particular line of code is doing.

3 But most bugs depend on how a line of code is executed.

4 The previous line of code compiles and executes correctly because there is an implied cast.

5 Sometimes, a line of code contains more than one executable statement.

6 In the Disassembly window, click on a line of code and choose Toggle Breakpoint from the Debug menu.

7 And then, on your last line of code, you return that variable to the calling program.

8 The report was brief, no more than a single line of coded message, yet it was significant.

9 With CSS you can change the color and size attributes by rewriting one line of code.

10 This box can be useful for distinguishing multiple breakpoints on the line of code.

11 Naturally this object isn't going to do much at this point, but it will initialize a single instance of a generic object based only on this line of code.

12 As you debug your code, you'll notice the middle view provides the PHP file with the active line of code currently being computed as highlighted.

13 From the list of SQL statements in the outline view, you can double click on any SQL statement to see which line of code created the SQL, or you can right click on the SQL and select Show in source.

14 In Virtual Space mode, spaces are inserted at the end of each line of code.

15 I've given Pixie the name of my object (Todo list), and asked it to be stored as well in this one line of code.

16 As we saw in this example, you can load and save data in one line of code .

17 Clicking this area sets a breakpoint on the adjacent line of code.

18 The instruction pointer will be on the first executable line of code in the object.