Original bug ID: 3767
Reporter: administrator
Status: acknowledged
Resolution: open
Priority: normal
Severity: feature
Category: tools (ocaml{lex,yacc,dep,debug,...})

Bug description

Full_Name: Nathan Gaylinn
Version: 3.08.3
OS: Linux
Submission from: point.cs.brown.edu (128.148.33.31)

Hello! I've been working on developing an OCaml IDE with a graphical debugger

all summer. My program will be released soon, but there are still many things I
would like to do to improve upon it and certain features I'd like to add.
When working with ocamldebug to create the graphical debugger, I ran into many
complications and difficulties. There were some places where my life would have
been easier with more or different information from ocamldebug. Also, there are
some very nice features I would like to add, but cannot because ocamldebug
itself cannot give me what I need.
With both my experience working with ocamldebug and my experience trying to
make a graphical interface to fit around it, I have prepared a wish list of
sorts describing several features (most of which I assume would be relatively
easy to add) that I would love to see in a future release of ocamldebug. I hope
you find my suggestions useful, and that they make it to an upcoming release.
Unfortunately, I'll have to stop major development on my IDE soon, so it would
be wonderful if these changes could happen in the near future. If not, though,
hopefully they will happen eventually and hopefully I'll have the time to add
support for them in my program when they do.

Anyway, without further ado, my wishlist:

When the program stops (user break, a breakpoint, a step command has finished,

etc.), give access to the expression that either has just been evaluated or is
about to be, not just the character. This is more clear, and makes it evident
what "display *" should return. Sometimes more than one expression ends at the
same character and it is ambiguous which has just been evaluated.

When describing an event (as in "info events Modulename"), give the full

expression and not just a character offset. In some cases, more than one event
can have the same character offset so there is no way to distinguish between
them without actually setting breakpoints and testing which is which. It would
be fine to just give a beginning and ending character offset, or a beginning
character offset and a length.

When deleting a breakpoint, give some responce to signify that the deletion was

successful. Something like "Removing breakpoint 1 at 15376 : file bignum.ml,
line 24, character 29" would be very nice.

Do something to distinguish between part of a backtrace and the description of

a stack frame when changing frames. Just adding "Backtrace: " before the list of
stack frames would be sufficient.

Add a command that can give the file name associated with a module name or visa

versa. It's confusing to set a breakpoint in module Bignum and see your code
break in the file bignum.ml. Also, this would be very useful for an IDE to be
able to know which file was associated with a which module.

Add the ability to ignore events ocurring in a given module. For instance,

almost no one cares if an event occurred in pervasives. It would be nice to be
able to turn off events in a set of modules, or even in all modules that are
part of the OCaml libraries. An IDE could add this feature, but it would be a
nice one to include within ocamldebug itself.

Thank you for your consideration,

-- Nate Gaylinn