On Wed, 2016-03-09 at 14:35 -0800, Ali Nematollahi wrote:
I'm not concerned about IPv6 at all. I'm running Kernel 3.12 Here is the backtrace: root beaglebone:~# gdb /usr/sbin/NetworkManager GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/g pl.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 "arm-linux-gnueabihf". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/NetworkManager...done. (gdb) run --debug --g-fatal-warnings Starting program: /usr/sbin/NetworkManager --debug --g-fatal-warnings [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux- gnueabihf/libthread_db.so.1". NetworkManager-Message: <info> No config file found or given; using /etc/NetworkManager/NetworkManager.conf [New Thread 0xb686b3c0 (LWP 2821)] (NetworkManager:2818): NetworkManager-WARNING **: <warn> glib- version: cannot handle SIGUSR1 and SIGUSR2 signals. Consider upgrading glib to 2.36.0 or newer
Hmpf, seems you cannot use --g-fatal-warnings because then NM dumps core on this warning. This would be fixed now on master https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b49322b568725c8c92c0732b14cc726748ec57d3 Can you try again without --g-fatal-warnings: export G_DEBUG=fatal-criticals gdb /usr/sbin/NetworkManager > run --debug Thomas
Attachment:
signature.asc
Description: This is a digitally signed message part