# get debug symbols and gdb $ sudo apt install numad-dbgsym gdb dpkg-dev # get source as used in the package $ apt source numad # I found that we will also need glibc source, so: $ apt source glibc
It helps to add paths to gdb (gdb) directory /home/ubuntu/numad-0.5+20150602:/home/ubuntu/glibc-2.27:/home/ubuntu/glibc-2.27/malloc I found these backtraces: Thread 1 "numad" received signal SIGSEGV, Segmentation fault. tcache_get (tc_idx=<optimized out>) at malloc.c:2943 2943 malloc.c: No such file or directory. (gdb) bt #0 tcache_get (tc_idx=<optimized out>) at malloc.c:2943 #1 __GI___libc_malloc (bytes=16) at malloc.c:3050 #2 0x00000d9b7ec780dc in bind_process_and_migrate_memory (p=0xd9b843b0f70) at numad.c:993 #3 0x00000d9b7ec7d148 in manage_loads () at numad.c:2225 #4 0x00000d9b7ec734dc in main (argc=<optimized out>, argv=<optimized out>) at numad.c:2654 (gdb) bt #0 0x00000fb6cd2779f4 in bind_process_and_migrate_memory (p=0xfb6fc1e0f70) at numad.c:998 #1 0x00000fb6cd27d148 in manage_loads () at numad.c:2225 #2 0x00000fb6cd2734dc in main (argc=<optimized out>, argv=<optimized out>) at numad.c:2654 (gdb) bt #0 0x000001c757da79f4 in bind_process_and_migrate_memory (p=0x1c758a60f70) at numad.c:998 #1 0x000001c757dad148 in manage_loads () at numad.c:2225 #2 0x000001c757da34dc in main (argc=<optimized out>, argv=<optimized out>) at numad.c:2654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832915 Title: numad crashes while running kvm guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1832915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
