# $Id$ -*- Text -*-
# The list of known (reproducible) DDD bugs.

Note: For problems occurring when *building* DDD, see the file `PROBLEMS'.
      For reported bugs that could not yet be reproduced, see `OPENBUGS'.

This is a list of known (i.e. reproducible) DDD bugs, which should be
fixed in some future DDD release.  

If you find a bug, be sure to report it to <bug-ddd@gnu.org>
such that we may fix it (or include it in this list :-)

If you want to fix some of these, please ask <ddd@gnu.org>
whether there are already people working on that bug.

Projects marked with an `*' are to be fixed in the next DDD release.
Volunteers for fixing these and other bugs are welcome!

-- list starts here --

001 It's too big and too slow.  [This one will never get fixed]

003 (Motif 1.1) The command window is scrolled whenever obscured.

021 (DBX) Using SunOS DBX, attempting to dereference a `(nil)' pointer
    results in an error message and no new display.  However, the
    expression is entered as an ordinary display.

026 (DBX) Using SunOS DBX with PASCAL or Modula-2, selected array
    elements are not counted from the starting index of the array.

041 Starting a multi-window DDD iconified under vtwm and fvwm causes
    trouble with group iconification.

126 Flashing data window.  Thomas Liefke
    <liefke@cdc.Informatik.TH-Darmstadt.DE> reports that the data
    window is flashing forever in certain circumstances. The flashing
    looks like a rapid, endless update of the data displayed. The
    flashing only occurs when the panner is used.  While the window
    (i.e. the boxes and the panner) is flashing, another panner is
    occurring in the upper left corner in each flash-cycle.

    The flashing does NOT occur when the scroll bar is used instead of a
    panner.

    How I can reproduce the bug:

    ddd ctest

    now I press:

    break at()
    run
    step
    click on variable 'tree' and select 'display'
    click on box 'tree' and select 'display*'
    click on 'data = {...}' and select 'show detail'

    make the data window smaller so that the lower box doesn't fit
    completely into window

    make the data window big enough for all three boxes.

    Then the window is flashing forever unless I make the window
    smaller and then bigger again.

    When I repeatedly change the size, the flashing comes again but
    not each time the window size is big enough to hold all boxes.

155 (DBX) `dump` output is not understood if local arrays are shown.
    (DBX prints these as `ARRAY')

249 Zdenek Sekera <zs@cray.com> reports:
    c. Some Makefiles in the subdirectories do not use CFLAGS thus
       making it neccessary to always edit them to put in the correct
       options.  This is very time consuming in particular on
       (e.g. myself) always forgets at least some little wee thing
       somewhere....
       [This is a problem of the libiberty and librx maintainers.  -AZ]

    d. In the same veine, when I run e.g. "configure --prefix='$(HOME)'",
       the $(HOME) does not get propagated to all Makefiles.
       [This is a problem of the libiberty and librx maintainers.  -AZ]

272 (LessTif) The `select' font selection method works only once.

281 In auto deiconify mode, the Debugger Console uniconifies even if
    other DDD windows are already there.

286 (Motif) Changing Cut/Copy/Paste accelerators at runtime does not work.

290 (Motif 1.1) The `Settings' dialog is too wide.

301 (LessTif 0.87) Changing preferences while the edit menu is torn
    off causes a core dump.

307 Marco Hess <marcoh@senet.com.au> says that sometimes, the source
    window locks in scroll mode until it reaches the top or bottom of
    the file.
    [Johan Vermeire <jvme@se.bel.alcatel.be> reports that
     lowering the `glyphUpdateDelay' resource fixes this.]

311 After `next 4' on Solaris DBX, the current position is not
    highlighted.

342 (Gnuplot/xlib) Using the builtin plot window, the plot points of
    different data files all have the same color.  This does not
    happen with the external Gnuplot window.

353 (Automake) The `configure' script checks for `__CYGWIN32__', but
    as of Beta 20, this should be `__CYGWIN__'.

360 Plot tear-offs remain active after the main window has been closed.

368 When DDD is running on a locked terminal (via `xlock' or
    likewise), DDD considers the pointer to be frozen, such that it
    continues execution.

370 Is the command shell raised each time a new display is created?

371 Reduce flickering when setting options.

373 In `Define Command', changing the `()' toggle does not change
    defined buttons.

375 Improve Python support (in DDD 3.2)

376 In DDD 3.2.90 and later, the resource

    Ddd*enableBtn1Transfer: False

    only works if the `Ddd' app-defaults file is installed.

382 (Insert new bugs here)
