Hey, > Tracing contains no information of values written to memory or registers. So > tracing only contains the stack information and the pc. That's not what I > need :-) > And the "trace output dump bla bla manager" is much stuff to replace a cout. > I have no idea what is the intention to make it so complicated. I implemented the new initial version of the new tracing code, and I believe ThomasK took over from there.
One reason was to support value change dump (.VCD) files (and selecting just a portion of pins to trace) in addition to the usual text, that you can then load into gtkwave. I believe that e.g. Markus Hitter was quite happy about having this? I have used it for some quite detailed protocol timing things using the VCD functionality. > And in addition, the code is still broken. The "manager" crashes after a few > seconds. If so, that's of course a bug and should be fixed. Cheers, Onno _______________________________________________ Simulavr-devel mailing list Simulavr-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/simulavr-devel
