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
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1532722
Title:
/sbin/ifup:11:__GI_strncpy:strncpy:do_interface:main
Status in ifupdown package in Ubuntu:
In Progress
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem
regarding ifupdown. This problem was most recently seen with version
0.8.6ubuntu1, the problem page at
https://errors.ubuntu.com/problem/6c970a32e2d96151cb8f99d98a460a42e697e6f2
contains more details.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1532722/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
