On 27 Jun 2006, at 12:35, Richard Stallman wrote:
normally
has several symbols on the same line. So here, one needs an arrow
pointing between the grammar symbols of each active rule.
We could surely modify GDB and gdb-ui.el to do that.
It could be that this feature is useful for C/C++ debugging as
well.
That would require a lot more debugging info. Right now the debugging
info generated for C is just line numbers. In practice that seems to
work well enough.
If debugging Bison grammars really needs this feature, then we can
provide it and use it for debugging Bison grammars. But we would not
want to use it for C.
It just seems me too primitive that one should have to modify the
source file, breaking the source code up on several lines just for
debugging purposes. One idea that come to my mind, is that one would
be enabled to provide an optional input debug file, detailing what
debugging information should be generated. So if more debugging
detail is needed in some segment, one puts that information into this
debug input file instead of modifying the source file.
As for Bison .y debugging, that is on a higher level, and I think it
would be too rude to not see the exact parsing position.
Hans Aberg
