On Tue, Jan 19, 2010 at 04:05:26PM +0800, Jie Zhang wrote: > gdb-comm.exp sets breakpoints on exit and abort before load. The > problem is that GDB tries to skip prologue according to what it > reads from memory, which might contain random data since the > executable has not been loaded into memory. In my case, sometimes > skip_prologue might skip one or two more instructions, which happens > to be an exception instruction and will trap the processor into an > exception event loop after running the executable before hit the > breakpoints. The attached patch changes gdb-comm.exp to set > breakpoints after load.
OK, thanks. Ben _______________________________________________ DejaGnu mailing list DejaGnu@gnu.org http://lists.gnu.org/mailman/listinfo/dejagnu
