Dumping the Log Files

To do efficient stepping through the call stack (stack dump) in a log file, you can re-dump them with CM in your Emacs compilation buffer. After that M-N (next-error) and C-M-N (previous-error) will work as usual!

This is how you do it (provided that you have CM running):

• Open up base/cm/win/develop/dumpStackFromFile.cm
• If the log is on your desktop and called log0.cmtxt, just run with C-M-P

If the file is called log, log1, or log2, you can run one of these instead:

{
    dumpStackFromDesktopLog();
    //dumpStackFromDesktopLog1();
    //dumpStackFromAppDataLog2();
}

Dumping Older Logs

Older log files from 10.0 and older are often renamed with an extra number. If you are working for example in a 10.0 extension and get log files from CET 10.5, a lot of the code will have changed, and thus the line numbers in the log file will not correspond very well to the code.

But if you have another workspace with the appropriate code in it, it's still possible to follow the log with a little tweaking. Let's say that I have the CET 10.5 release branch in the workspace that I'm not using right now, located in C:\CetDev\version10.5, then I can use these files when analyzing the log. I just edit in this:

/**
 * CM base - you can replace this to make next error point at another workspace etc.
 */
//private const str base = "\n" # cmUrl("").toS;
private const str base = "\nC:\CetDev\version10.5\\";

And that way next-error will work a lot better!