On 19/01/2010 07:36, 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.
Something is wrong here. Before the inferior is started, gdb should be
looking at the prologue bytes from the executable image file, not the inferior
memory. Is something going wrong in gdb_comm_file_cmd()?