Re: debugger 6.2.1 misfeatures

[Michael Chastain <mec dot gnu at mindspring dot com>]

Sounds like a bug to me.

Generally for a bug, we need:

  the gdb version
  the host operating system version
  the target operating system version (if it's not the same as the host)
  a typescript of the whole gdb session showing the bug
    (use the 'script' command)
  some info about the inferior program:
    what language it's written in
    the exact compiler name and compiler version that it was built with

Then if somebody picks up the bug, they're likely to come back with
more questions.  The point at this stage is not to identify the bug,
but just to throw enough information over the fence so that the
gdb engineer can *reproduce* the bug.

If it worked with a previous version of gdb, that's good to know.

It's really great if you can supply a small test program
(source + binary) that demonstrates the bug.

And some bug reports are successful and get fixed, and some aren't
and don't.

Michael Chastain