strace end of output of the `dkms ldtarball ...` command :
```
...
14013 close(1) = 0
14013 close(2) = 0
14013 exit_group(0) = ?
14013 +++ exited with 0 +++
13918 <... wait4 resumed> [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) =
14013
13918 rt_sigaction(SIGINT, {sa_handler=0x555b7f3f60, sa_mask=[], sa_flags=0},
{sa_handler=0x555b7d76f8, sa_mask=[], sa_flags=0}, 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=14013,
si_uid=0, si_status=0, si_utime=0, si_stime=0} ---
13918 wait4(-1, 0x7fc3f20120, WNOHANG, NULL) = -1 ECHILD (No child processes)
13918 rt_sigreturn({mask=[]}) = 0
13918 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
13918 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
13918 exit_group(1) = ?
13918 +++ exited with 1 +++
```
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1002657
Title:
dkms ldtarball has bad exit status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1002657/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
