Martin Pitt wrote: > Also, just for kicks, does arecord work in memory mapped mode, thus with > -M?
Hold on! It does not, but it do fail with an error. It just sit there, not exiting despite -d 3 and spin. If I strace the running process, I get:
etienne@curst:~$ strace -p 7019 Process 7019 attached - interrupt to quit restart_syscall(<... resuming interrupted call ...>
If I kill arecord with Ctrl-C, the test.wav is empty.
Attaching the output of strace -f -o /tmp/arecord-memmap.strace -s 1024 -v arecord -M -D hw:1,0 -d 3 -f cd -t wav test.wav
Martin Pitt wrote:
> Also, just for kicks, does arecord work in memory mapped mode, thus with
> -M?
Hold on! It does not, but it do fail with an error. It just sit there,
not exiting despite -d 3 and spin. If I strace the running process, I get:
etienne@ curst:~ $ strace -p 7019 syscall( <... resuming interrupted call ...>
Process 7019 attached - interrupt to quit
restart_
If I kill arecord with Ctrl-C, the test.wav is empty.
Attaching the output of strace -f -o /tmp/arecord- memmap. strace -s 1024
-v arecord -M -D hw:1,0 -d 3 -f cd -t wav test.wav