Re: Bison and C++

[Richard Stallman]

    If it is the same feature we are speaking about: What I meant is that the
    arrow points at the .y source file when stepping around. So one should see
    the Bison rules with an arrow.

I believe that works, thanks to the #line directive.

    When a regular C/C++ source is compiled, the CW, apart from the object .o
    file, also writes a special .sym file with information for the debugger
    about which names should be debugged, their format, and so on, sufficient
    for debugging.

I am not sure what "which names should be debugged" means.

GCC also outputs information about all the variable names and their
data types, and this too should be "sufficient for debugging".
This is what -g does.  However, it could be that the other compiler
includes a particular kind of information which GCC does not generate.
If so, we might be able to think about adding something additional
*if you could give a more specific suggestion*.

    First, you must understand that I have not used GDB for a few years. When I
    used it, I recall one had to use special command to write in the source
    file; there were separate debugging source files one had to write .

I am not sure what you mean, but I don't believe this is true with GDB.

    Now to the debugging: If the debugger only handles C++ static typing, it
    will show that  ap  is an  A, and will only display that structure of it
    (the names in that class and their values).

    But if the debugger handles C++ dynamic data, it will show that the  ap  is
    actually a  B, and will show that (the names in that class  B  and their
    values).

That is specific enough that I can pass it along to the GDB developers.
Thanks.