Segmentation fault about cinf HOT 15 CLOSED

@mhausenblas
root@client0:# cinf
Segmentation fault
root@client0:# cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
root@client0:# docker --version
Docker version 1.12.2, build bb80604
root@client0:# uname -a
Linux client0 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

from cinf.

@JoshuaAndrew thanks for raising this issue, can you be a bit more specific concerning your environment pls? What system, for starters (uname -a)?

from cinf.

@JoshuaAndrew thanks. Quick question: does it also happen if you're not root but execute it with sudo?

from cinf.

@mhausenblas
joshua@client0:$ sudo DEBUG=true cinf
joshua@client0:$ sudo cinf
joshua@client0:$ sudo cinf
joshua@client0:$
joshua@client0:$
joshua@client0:$

no output!

from cinf.

Strange. Just tried to reproduce it but works fine for me 8->

What version are you on, that is, what version does cinf --version report?

from cinf.

joshua@client0:$ sudo cinf --version
joshua@client0:$
joshua@client0:$ sudo cinf --version
joshua@client0:$

no output too! well I installed v0.4.0-alpha

from cinf.

OK, that really is strange, one would expect that it can at least output its version. @JoshuaAndrew two more things to check (running slowly out of ideas what the cause could be here): can you execute cinf alone (that is, without sudo) and what is the output there. Also, maybe related, what does sudo apparmor_status give?

from cinf.

Are you still having this problem @JoshuaAndrew? Otherwise I'm closing this for now …

from cinf.

@mhausenblas

joshua@client0:$ cinf
Segmentation fault
joshua@client0:$ sudo apparmor_status
apparmor module is loaded.
21 profiles are loaded.
21 profiles are in enforce mode.
/sbin/dhclient
/usr/bin/evince
/usr/bin/evince-previewer
/usr/bin/evince-previewer//sanitized_helper
/usr/bin/evince-thumbnailer
/usr/bin/evince-thumbnailer//sanitized_helper
/usr/bin/evince//sanitized_helper
/usr/lib/NetworkManager/nm-dhcp-client.action
/usr/lib/connman/scripts/dhclient-script
/usr/lib/cups/backend/cups-pdf
/usr/lib/lightdm/lightdm-guest-session
/usr/lib/lightdm/lightdm-guest-session//chromium
/usr/lib/telepathy/mission-control-5
/usr/lib/telepathy/telepathy-*
/usr/lib/telepathy/telepathy-//pxgsettings
/usr/lib/telepathy/telepathy-//sanitized_helper
/usr/lib/telepathy/telepathy-ofono
/usr/sbin/cups-browsed
/usr/sbin/cupsd
/usr/sbin/tcpdump
docker-default
0 profiles are in complain mode.
12 processes have profiles defined.
12 processes are in enforce mode.
/usr/sbin/cups-browsed (1064)
/usr/sbin/cupsd (4134)
docker-default (23250)
docker-default (23273)
docker-default (23283)
docker-default (23284)
docker-default (23286)
docker-default (23287)
docker-default (23288)
docker-default (23289)
docker-default (23290)
docker-default (23291)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.

suggest you look at this article: https://en.wikipedia.org/wiki/Segmentation_fault
I guess it's a fault of the program itself.

from cinf.

@JoshuaAndrew we still haven't found the cause (and thanks, yeah, I know what a seg fault is but that doesn't help me since I have nothing to go on). The fact that apparently it does produce zero output when you call it without sudo and as a non-root user, even for the simple case of printing its own version is very odd. Since I can't reproduce the issue, only thing I can suggest is that you try it out on a different system.

from cinf.

OK, one more thing we could try @JoshuaAndrew … can you do strace cinf or sudo strace cinf whatever gives an actual output and no seg fault?

from cinf.

joshua@client0:$ sudo strace cinf
execve("/usr/local/bin/cinf", ["cinf"], [/* 24 vars _/]) = -1 EFAULT (Bad address)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_USER, si_pid=1282, si_uid=0} ---
+++ killed by SIGSEGV +++
joshua@client0:$
joshua@client0:$
joshua@client0:$
joshua@client0:$
joshua@client0:$ strace cinf
execve("/usr/local/bin/cinf", ["cinf"], [/_ 30 vars */]) = -1 EFAULT (Bad address)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_USER, si_pid=1316, si_uid=1000} ---
+++ killed by SIGSEGV +++
Segmentation fault (core dumped)

from cinf.

@JoshuaAndrew thanks! Just to make sure I understand, you did install the binary via curl -s -L https://github.com/mhausenblas/cinf/releases/download/v0.4.0-alpha/cinf -o cinf, right?

from cinf.

@JoshuaAndrew can you let me know if you used the binary I provided or built it yourself? Otherwise I consider this a wontfix …

from cinf.

OK, closing for now since I can't reproduce it and don't have further info as to what the root cause might be. We can re-open it if some new infos come up.

from cinf.