Bug#630944: dd can't seek and read in /proc/self/mem

pac...@kosh.dhis.org hat am Mon 27. Jun, 23:02 (-0500) geschrieben: =?iso-8859-1?Q?J=F6rg?= Sommer writes: I don't know, why dd thinks something went wrong. llseek() and fstat64() didn't return an error. Accessing the file with Ruby yields the expected result. I don't speak ruby, but

Bug#630944: dd can't seek and read in /proc/self/mem

=?iso-8859-1?Q?Jörg?= Sommer writes: pac...@kosh.dhis.org hat am Mon 27. Jun, 23:02 (-0500) geschrieben: =?iso-8859-1?Q?J=F6rg?= Sommer writes: I don't know, why dd thinks something went wrong. llseek() and fstat64() didn't return an error. Accessing the file with Ruby yields the

Bug#630944: dd can't seek and read in /proc/self/mem

=?iso-8859-1?Q?J=F6rg?= Sommer writes: Package: coreutils Version: 8.5-1 Severity: normal Hi, I wanted to extract the vdso segment, but dd can't work in /proc/self/mem. The kernel restricts use of /proc/PID/mem to the process that is currently ptrace'ing (debugging) PID. dd can't do

Bug#630944: dd can't seek and read in /proc/self/mem

Package: coreutils Version: 8.5-1 Severity: normal Hi, I wanted to extract the vdso segment, but dd can't work in /proc/self/mem. % grep vdso /proc/$$/maps 0010-00103000 r-xp 00:00 0 [vdso] % strace -o /tmp/dd.st dd if=/proc/$$/mem of=/tmp/vdso skip=$((0x0010/4096))