Dumping the parse tree of a GLR parser

[Kelly Leahy]

I'm using a GLR parser, and I see that when there is
an ambiguity during parsing that is not resolved by
precedence or merging rules, it is printed to the
output (when YYDEBUG is enabled with yydebug != 0)
using the function yyreportTree(...).

Is there some way I can call yyreportTree in my
top-level rule (start production for my grammar) to
dump the tree myself, or is that information no longer
available once the stacks have been merged back into a
single stack?

I would really like to be able to see this information
for debugging purposes, even when the parse was
unambiguous, but every attempt I've made at trying to
call this function results in a bus error because I'm
sure I haven't figured out which expression to use for
the first argument.

Thanks,
Kelly