Re: debugging a callq command

On 07/06/2018 12:32 PM, Mahmood Naderan via gdb wrote:
> As you can see, the first instruction is a jmp to 0x7fffffffde7d and there, it will call 0x7fffffffde70. However, the next instruction is something else while the program receives seg fault.

Are you maybe confusing stepi with nexti?  nexti steps over the call
instruction, and then it sounds like something crashes within the
called routine at 0x7fffffffde70.  Try "stepi" to follow the full
instruction flow instead, and it will probably crash at the same
instruction.

Thanks,
Pedro Alves