This should only happen when calling with --no-act, i. e. when being called as "ifquery", as I don't think we regularly call ifup with --no- act. It's also in the "if (cmds == iface_query)" code path.
When trying to recreate this on my amd64 laptop, gdb shows that current_state gets initialized to NULL. However, the crashes on errors.ubuntu.com are all on armhf, where the local stack variable apparently just happens to be non-zero. I can force this behaviour by changing the initialization to char *current_state = (char*) 1; then sudo rm /run/network/ifstate.lo $ ./ifquery lo crashes in this manner. So the solution is rather simple -- initialize current_state. ** Changed in: ifupdown (Ubuntu) Status: New => Triaged ** Changed in: ifupdown (Ubuntu) Status: Triaged => In Progress ** Changed in: ifupdown (Ubuntu) Importance: Undecided => High ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532722 Title: /sbin/ifup:11:__GI_strncpy:strncpy:do_interface:main To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1532722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs