On Tue, Oct 25, 2005 at 10:08:59AM +0200, Christophe LYON wrote: > On occasions, I wonder whether it wouldn't make sense to generate > different infos in debug_frame and eh_frame: IIUC, GCC tries to > 'compress' the debug frame info by generating few advance_loc > instructions (eg only 1 for the whole prologue), which makes sense in > the C++ EH stack unwinding context, but my cause problems in a debugger.
No it doesn't. Look closer at the optimization. It compresses the advances only when the original register is still unmodified. r~
