I'm really glad you pointed out the vs.log! Here's the last entry from the vs.log, all the previous entries were from applying hotfixes to 13.0.2, so I'd guess that the log isn't cleared when migrating a profile. Seems like it should be, IMO.
EDIT: I really need to move on with getting my tasks done, so I'm going to have to defer looking any deeper into this for a while. It seems that the radio button for Symbol compare, present in 2008, was removed for 2009. I tried to have it compare the appropriate line ranges in the same file, and that's how I ended up with the stack. The lines that were actually compared were not the ones I selected, though I don't remember specifically how they were wrong. I think the lines on the right side were completely wrong.
Slick-C STACK TRACE ******************************
Created on 3/24/2009 at 9:7:5 (175 ms)
SlickEdit Version 14.0.0.5 Copyright 1988-2009 SlickEdit Inc.
Edit module and type "st -f <offset>" to get the
run-time error position
error code=-3073
Invalid pointer argument
SymbolColorAnalyzer.ex 2809 se.color.SymbolColorAnalyzer.colorLines(
1: [5]=<empty>
2: 1
3: 78
4: 1
p_window_id: 54
p_object: OI_IMAGE
p_name:
SymbolColorAnalyzer.ex 4303 _UpdateSymbolColoring(0) p_window_id: 54 p_object: OI_IMAGE p_name:
autosave.ex 496 _as_callback() p_window_id: 54 p_object: OI_IMAGE p_name:
Slick-C STACK TRACE ******************************
Created on 3/30/2009 at 17:7:52 (5 ms)
SlickEdit Version 14.0.0.7 Copyright 1988-2009 SlickEdit Inc.
Edit module and type "st -f <offset>" to get the
run-time error position
error code=-3015
Invalid argument
bufftabs.ex 4209 _update_mod_file_status() p_window_id: 5 p_object: OI_FORM p_name:
autosave.ex 466 _as_callback() p_window_id: 124 p_object: OI_EDITOR p_name: