Find the command to fail assembly from the main dump in Linux

If I load a failed program and a kernel dump in gdb, it shows me the stack trace and the point of failure, as shown below.

Core was generated by `./cut --output-d=: -b1,1234567890- /dev/fd/63'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  is_printable_field (i=1234567890) at src/cut.c:266
266   return (printable_field[n] >> (i % CHAR_BIT)) & 1;
(gdb) bt
#0  is_printable_field (i=1234567890) at src/cut.c:266
#1  set_fields (fieldstr=0x7ffccb0561c4 "") at src/cut.c:533
#2  main (argc=4, argv=0x7ffccb055cf8) at src/cut.c:865

Is there any means to get the exact assembly instructions that caused segfault?

+4
source share
2 answers

Installation is possible:

(gdb)layout asm

When the GDB stops, the corresponding assembly line is indicated.

Example:

   │0x7ffff7aa441d <strtok+45>      je     0x7ffff7aa44d6 <strtok+230>
   │0x7ffff7aa4423 <strtok+51>      mov    %rsi,%rax                                                                                                         │
  >│0x7ffff7aa4426 <strtok+54>      mov    (%rax),%cl                                                                                                        │
   │0x7ffff7aa4428 <strtok+56>      test   %cl,%cl                                                                                                           │
   │0x7ffff7aa442a <strtok+58>      je     0x7ffff7aa4454 <strtok+100>


Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7aa4426 in strtok () from /lib64/libc.so.6
(gdb) 
+3
source

You can use the disassemblegdb command . Also use x/iin $rip(program counter on x86-64)

, C ( ++ operator []), printable_field n.

valgrind / ( -g -Wall GCC -fsanitize=..., -fsanitize=address -fsanitize=undefined...

+2

Source: https://habr.com/ru/post/1624926/


All Articles