x32: gdbserver's agent bytecode JIT: fix "call" emission
authorPedro Alves <palves@redhat.com>
Fri, 19 Aug 2016 11:07:45 +0000 (12:07 +0100)
committerPedro Alves <palves@redhat.com>
Fri, 19 Aug 2016 11:12:18 +0000 (12:12 +0100)
commited036b4052193ba6790ba7ee94a33a364ace3b55
treea8555c4f79efed4c46f0e7dde1564798a72cede9
parentc8ef42eed100c2439e600e846caa7437da93ac17
x32: gdbserver's agent bytecode JIT: fix "call" emission

Running fast tracepoint tests on x32 exposes a latent bug in the agent
bytecode jitting.  There's a code path that forgets to emit the call
opcode...  Whoops.  Fixes a bunch of gdb.trace/trace-condition.exp
FAILs, like:

  (gdb)
  continue
  Continuing.

  Thread 1 "trace-condition" received signal SIGSEGV, Segmentation fault.
  0x7ffec016 in ?? ()
  (gdb) FAIL: gdb.trace/trace-condition.exp: ftrace: $rip == *set_point: advance through tracing

gdb/gdbserver/ChangeLog:
2016-08-19  Pedro Alves  <palves@redhat.com>

* linux-x86-low.c (amd64_emit_call): Emit missing call opcode.
gdb/gdbserver/ChangeLog
gdb/gdbserver/linux-x86-low.c