Marking as Invalid as that seems expected: strace uses ptrace which does
not work across setuid/setgid binaries which crontab is.
-rwxr-sr-x 1 root crontab 43K Jun 6 2024 /usr/bin/crontab
This is intended for security (otherwise it would be trivial to hijack
`su`).
** Changed in: strace (Ubunt
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: strace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/582319
Title:
stra
Interesting to note that strace is actually changing the output of
crontab -e in debian 4.0 (perhaps by calling isatty somewhere?), just
not the return value. So it could be that a bug with crontab -e
returning the right value was fixed in the 2008-2010 timeframe instead
of a bug being introduced
Looks like the change was made between 2008 and 2010...
debian-4.0$ export EDITOR=cat ; crontab -e ; ret1=$? ; strace crontab -e ;
ret2=$? ; echo ; echo return: $ret1, straced return: $ret2
... [snip] ...
return: 0, straced return: 0
debian-5.0$ export EDITOR=cat ; crontab -e >/dev/null ; ret1=$
attached is the strace.out generated from the above script
** Attachment added: "strace.out"
http://launchpadlibrarian.net/48666960/strace.out
--
strace crontab -e bombs on 10.04LTS
https://bugs.launchpad.net/bugs/582319
You received this bug notification because you are a member of Ubuntu
Bu
** Attachment added: "typescript output showing the bug"
http://launchpadlibrarian.net/48666943/typescript
--
strace crontab -e bombs on 10.04LTS
https://bugs.launchpad.net/bugs/582319
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
