kdbg/doc/en/tips.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
   2 <html>
   3 <head>
   4    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   5    <meta name="Author" content="Johannes Sixt">
   6    <title>KDbg - User's Manual - Tips and Tricks</title>
   7 </head>
   8 <body text="#000000" bgcolor="#FFFFFF">
   9 <p><a href="index.html">Contents</a></p>
  10 <h1>
  11 Tips and Tricks</h1>
  12
  13 <ul>
  14 <li>
  15 You can use breakpoints as bookmarks: Just set a breakpoint and disable
  16 it. Later, you can quickly come back to that breakpoint by double-clicking
  17 it in the breakpoint list (or select it and click <i>View Code</i>). Since
  18 breakpoints are persistent (i.e. KDbg remembers them across invocations
  19 of a program), you get them back next time you invoke KDbg for that particular
  20 program.</li>
  21
  22 <li>
  23 You can display a value in the watch section in different ways by prepending
  24 gdb's format specifiers in front of the variable to display. E.g. <tt>/x
  25 var.member</tt> displays the <tt>var.member</tt> in hexadecimal notation.</li>
  26
  27 <li>
  28 You can set breakpoints in a source files that belong to a shared library.
  29 Such breakpoints will be marked as <em>orphaned</em> if the program is not active.
  30 <A href="breakptlist.html#orphanedbp">Orphaned breakpoints</A> are not effective.
  31 In order to make them effective, the program must stop at a time when the shared
  32 library is loaded. For this it is usually sufficient to set a breakpoint in
  33 <tt>main()</tt>. At the time when this breakpoint is hit, the orphaned breakpoints
  34 in the shared library become effective.</li>
  35 </ul>
  36
  37 </body>
  38 </html>