When I run the command
on a Linux 2.0.29 box, I get a segmentatation fault. I am unable to
duplicate this on other 2.0.X systems. Unfortunately, the bug seems
somewhat random and only occurs with these combined options.
Using strace, I have determined that the majority of the time the sigsegv
occurs during the proc read phase and never gets to the write phase but
that is not always the case.
This probably is not life-threatening in and of itself but it could lend
to a bigger problem which is why I would like any input that you might