История изменений

Исправление ~~Einstok_Fair~~, 07.07.18 15:33 (текущая версия) :

я не умею пользоваться gdb, что делать дальше?

$ coredumpctl gdb
           PID: 19592 (test)
           UID: 1000 (user)
           GID: 1001 (user)
        Signal: 11 (SEGV)
     Timestamp: Sat 2018-07-07 14:48:55 MSK (37min ago)
  Command Line: ./test
    Executable: /home/user/asmtest/test
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (user)
       Boot ID: 453a4e91959547cc891ae1668783d8e2
    Machine ID: 8ae3444f6ee746c6842365ac6c8850d8
      Hostname: sabayon.local
       Storage: /var/lib/systemd/coredump/core.test.1000.453a4e91959547cc891ae1668783d8e2.19592.1530964135000000.lz4
       Message: Process 19592 (test) of user 1000 dumped core.

GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/user/asmtest/test...(no debugging symbols found)...done.
[New LWP 19592]
Core was generated by `./test'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000001 in ?? ()
(gdb)

https://stackoverflow.com/questions/8305866/how-to-analyze-a-programs-core-dump-file-with-gdb

(gdb) where
#0  0x0000000000000001 in ?? ()
#1  0x00007ffc5b963b4c in ?? ()
#2  0x0000000000000000 in ?? ()
(gdb) bt full
#0  0x0000000000000001 in ?? ()
No symbol table info available.
#1  0x00007ffc5b963b4c in ?? ()
No symbol table info available.
#2  0x0000000000000000 in ?? ()
No symbol table info available.

Исправление ~~Einstok_Fair~~, 07.07.18 15:30:

я не умею пользоваться gdb, что делать дальше?

$ coredumpctl gdb
           PID: 19592 (test)
           UID: 1000 (user)
           GID: 1001 (user)
        Signal: 11 (SEGV)
     Timestamp: Sat 2018-07-07 14:48:55 MSK (37min ago)
  Command Line: ./test
    Executable: /home/user/asmtest/test
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (user)
       Boot ID: 453a4e91959547cc891ae1668783d8e2
    Machine ID: 8ae3444f6ee746c6842365ac6c8850d8
      Hostname: sabayon.local
       Storage: /var/lib/systemd/coredump/core.test.1000.453a4e91959547cc891ae1668783d8e2.19592.1530964135000000.lz4
       Message: Process 19592 (test) of user 1000 dumped core.

GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/user/asmtest/test...(no debugging symbols found)...done.
[New LWP 19592]
Core was generated by `./test'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000001 in ?? ()
(gdb)

https://stackoverflow.com/questions/8305866/how-to-analyze-a-programs-core-dump-file-with-gdb

Исправление ~~Einstok_Fair~~, 07.07.18 15:30:

я не умею пользоваться gdb, что делать дальше?

$ coredumpctl gdb
           PID: 19592 (test)
           UID: 1000 (user)
           GID: 1001 (user)
        Signal: 11 (SEGV)
     Timestamp: Sat 2018-07-07 14:48:55 MSK (37min ago)
  Command Line: ./test
    Executable: /home/user/asmtest/test
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (user)
       Boot ID: 453a4e91959547cc891ae1668783d8e2
    Machine ID: 8ae3444f6ee746c6842365ac6c8850d8
      Hostname: sabayon.local
       Storage: /var/lib/systemd/coredump/core.test.1000.453a4e91959547cc891ae1668783d8e2.19592.1530964135000000.lz4
       Message: Process 19592 (test) of user 1000 dumped core.

GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/user/asmtest/test...(no debugging symbols found)...done.
[New LWP 19592]
Core was generated by `./test'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000001 in ?? ()
(gdb)



https://stackoverflow.com/questions/8305866/how-to-analyze-a-programs-core-dump-file-with-gdb

Исходная версия ~~Einstok_Fair~~, 07.07.18 15:27:

я не умею пользоваться gdb, что делать дальше?

$ coredumpctl gdb
           PID: 19592 (test)
           UID: 1000 (user)
           GID: 1001 (user)
        Signal: 11 (SEGV)
     Timestamp: Sat 2018-07-07 14:48:55 MSK (37min ago)
  Command Line: ./test
    Executable: /home/user/asmtest/test
 Control Group: /user.slice/user-1000.slice/session-3.scope
          Unit: session-3.scope
         Slice: user-1000.slice
       Session: 3
     Owner UID: 1000 (user)
       Boot ID: 453a4e91959547cc891ae1668783d8e2
    Machine ID: 8ae3444f6ee746c6842365ac6c8850d8
      Hostname: sabayon.local
       Storage: /var/lib/systemd/coredump/core.test.1000.453a4e91959547cc891ae1668783d8e2.19592.1530964135000000.lz4
       Message: Process 19592 (test) of user 1000 dumped core.

GNU gdb (Gentoo 8.1 p1) 8.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/user/asmtest/test...(no debugging symbols found)...done.
[New LWP 19592]
Core was generated by `./test'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000000001 in ?? ()
(gdb)