Ladebug GUI FAQ


To send mail to the maintainer: ladebug support

GUI Questions

How do I change fonts?


Can I put the debugger output area in its own window?


I closed the Source Viewer Panel. How do I get it back?


How do I resize panels?


Why are + and - buttons used instead of window shade controls to resize panels?


How do I get the best known fonts and window sizes for the window system I display the GUI on?


How can I retain my main window size?


How do I turn off tool tips?


How do I set breakpoints using the GUI?


Why does the GUI beep when I type in a command?


What are the F2 and F3 buttons in the Source Viewer?


How do I graphically view an array?


I'm debugging a multithreaded application and have multiple Source Viewers displayed. When I print from the command input area, I don't get the result I expect. Why?


I get the message "Error: Can't open display:" when I try to run the debugger. What's wrong?


When typing in the GUI, the backspace key doesn't work as expected. How can I fix this?

How do I change fonts?

You can choose specific fonts for areas of the GUI; for example, you can choose a font to be used in the Source Viewer content area or the Debugger Output area. Be aware, however, that the chosen font may not work across platforms. To change the font, perform the following steps:

  1. Choose Edit->Preferences from the menu bar in the main window.
  2. In the preferences dialog, choose the Fonts radio button.
  3. Click on the Browse button next to the text field for the font that you want to change (for example, Source viewer font, or Debugger output font). A font selection dialog appears in which you can choose the font.
  4. Click on Apply in the preferences dialog. The Source Viewer and/or Debugger Output Area currently displayed will be updated with the chosen font.
  5. You may need to do this several times until you get a font that looks good on your display platform.
  6. When you find one, click on Cancel to remove the dialog.

Note that you could have clicked on OK in step 5, but if the font wasn't what you wanted, you would have to start at step 1.

The preferences dialog modifies an X resource file called ~/ladebugresource.


Can I put the debugger output area in its own window?

The debugger output area (and the command line input area) can be put in a separate window. To do this, perform the following steps:

  1. Choose Edit->Preferences from the menu bar in the main window.
  2. In the preferences dialog choose the Panels radio button.
  3. Choose Debugger Output from the option menu (a widget like a combo box).
  4. Check the box that says "Always create panel in new window" and click on OK or Apply.
  5. Close the Debugger Output Panel under the Source Viewer Panel (click on the X button in the top left corner of the panel).
  6. Choose View->Debugger Output from the main window. The Debugger Output Panel now displays in its own window.


I closed the Source Viewer Panel. How do I get it back?

Choose View->Current Source from the menu bar in the window.


How do I resize panels?

There are two ways to resize a panel:

  1. If the panel is in its own dialog, you can simply stretch the window.
  2. If the panel is within the main window, there are buttons with + and - on them. These buttons will increment or decrement the height of the widget they are near (typically lists or text output areas). The width can always be changed by stretching the window.


Why are + and - buttons used instead of window shade controls to resize panels?

The GUI uses the Motif widget set. Implementation issues prevent us from taking advantage of the window shade controls that are in Motif. Specifically, the use of window shade controls require that the panels be pre-built before being displayed. Our implementation relies on run-time building of panels. Major rework of the layout management software would be necessary to allow the use of window shades.

Many panels that make use of these controls have preferences you can use to change the preferred height, as follows:

  1. Size the Source Viewer, stack frames list, and/or the Debugger Output Panel using the + and - buttons.
  2. Choose Edit->Preferences from the menu bar in the main window.
  3. In the preferences dialog, choose the Panels radio button.
  4. The Debugger Output and the Source Viewer options should already reflect the settings you chose.
  5. Click on OK or Apply.


How do I get the best known fonts and window sizes for the window system I display the GUI on?

By default the GUI tries to use the best known fonts and window sizes for Tru64 (Motif). However, if you are displaying to a Linux system, or through eXcursion, for example, the fonts and window sizes may not be optimal. To select the best known fonts and window sizes for a particular "windowing system":

  1. Choose Edit->Preferences from the menu bar in the main window.
  2. In the General pane (it should already be visible), you will see an option menu labeled Window System Settings. It should be set to As is, which indicates the current settings.
  3. You can choose another window system (Linux, ReflectionX, Exceed, eXcursion, or Tru64). When a different setting is chosen, fonts and/or window sizes may be changed in some of the other panes.
  4. Click on OK or Apply. The main window will reflect the changes in font and/or window size. Remember that you can further tailor your settings by choosing the other radio buttons and changing the settings in those panes.


How can I retain my main window size?

  1. Size the main window to the desired width and height. Position the window where you want it to initially be displayed.
  2. Choose Edit->Preferences from the menu bar in the main window.
  3. Choose the Windows radio button. The window position, size, and height you resized/moved to should be reflected.
  4. If you want the window position to be saved, you must check the toggle that says "Set position of main window"
  5. Click on OK or Apply.


How do I turn off tool tips?

  1. Choose Edit->Preferences from the menu bar in the main window.
  2. Choose the General radio button (it may already be selected).
  3. Clear the toggle that says "Enable tool tips".


How do I set breakpoints using the GUI?

There are two ways to set breakpoints through the GUI:

  1. Click on the breakpoint buttons in the Source Viewer.
  2. Use the breakpoint creation wizard.
There are two ways to access the breakpoint creation wizard:
  1. Choose File->New Breakpoint to display the wizard.
  2. Choose View->Breakpoints to display existing breakpoints. When that dialog appears, click on the New button to display the wizard.


Why does the GUI beep when I type in a command?

This only happens when running the debugger under eXcursion. At this time, the reason is undetermined.


What are the F2 and F3 buttons in the Source Viewer?

The F2 and F3 buttons are "free" buttons that you can customize. For example, enter the following commands in your .ladebugrc or .dbxinit file, or on the command line:

	alias F2 "print *"
	alias F3 "whatis"
Now you can choose a pointer variable in your Source Viewer, click on F2, and the GUI will execute print * on the selection.


How do I graphically view an array?

Only two-dimensional numeric arrays can be graphically viewed at this time. To do so, enter the following in the command input area where <2-d array> is the array you want to view:

    view <2-d array>
The GUI displays a dialog with the graphical representation of the array.


I'm debugging a multithreaded application and have multiple Source Viewers displayed. When I print from the command input area, I don't get the result I expect. Why?

If you have more than one Source Viewer displayed on different threads and only one Debugger Output area in its own window, printing variables from the command input area may not yield the expected result. This is because the debugger engine's notion of the current thread and frame is dependent upon what the current thread and frame was during the last debugger event.

The current workaround is to click on the selected frame in the Source Viewer where you want to print. Then issue the command.


I get the message "Error: Can't open display:" when I try to run the debugger. What's wrong?

Your DISPLAY environment variable is not set. Do one of the following:

Another common problem is that, even though your display variable is set, the host you are trying to display to refuses the connection. To correct this problem, do the following:

  1. Telnet to the machine you want to display to (if not already logged in there).
  2. Enter:
    	xhost +the-host-you-are-running-from
    

When typing in the GUI, the backspace key doesn't work as expected. How can I fix this?

To date this problem has only been encountered when displaying the debugger to a PC via eXcursion. However, since the odd behavior is caused by X server configuration settings, it seems likely a user could encounter this problem under other PC X server applications.

To resolve this problem for the eXcursion v7 X server:

  1. Open the control panel for eXcursion via the Windows Start menu.
           Start->Programs->eXcursion v7->eXcursion Control Panel
  2. At the top of the Control Panel, click on the XWindow tab.
  3. In the Window Management group box, check the "Allow Foreign Window Managers" checkbox.
  4. Click on the Apply button (found on right side of panel).
  5. Click on the OK button (found on bottom of panel).