#3440 SIGPIPE in [exec] on HP-UX

obsolete: 8.4.13
closed-works-for-me
5
2014-08-28
2006-06-01
No

Hi *,

on HP-UX B.11.11 9000/800 running a plain tclsh 8.4.13,
the following behavior can be observed:

% exec cat file1 | dd bs=1 count=530 of=file2 2>/dev/null
child killed: write on pipe with no readers
% set errorInfo
child killed: write on pipe with no readers
while executing
"exec cat file1 | dd bs=1 count=530 of=file2 2>/dev/null"
% set errorCode
CHILDKILLED 19309 SIGPIPE {write on pipe with no readers}

whereas file1 is about 120kB. It works on Linux,
Solaris and AIX. Also running that pipe in a shell,
doesn't raise any errors.

I have a workaround, but that SIGPIPE should not occur.

kind regards -- Matthias Kraft

Discussion

  • Donal K. Fellows

    Logged In: YES
    user_id=79902

    http://tip.tcl.tk/16.html describes the maintenance areas;
    the area of a manual page associated with a problematic
    command is usually a good guide to what area to use.

     
  • Donal K. Fellows

    • labels: 105657 --> 24. Channel Commands
    • assigned_to: dkf --> hobbs
     
  • Joe English

    Joe English - 2006-06-29

    Logged In: YES
    user_id=68433

    This looks like expected (or at least acceptable) behavior
    to me. If the 'cat' process isn't finished writing when the
    'dd' process exits, it _should_ get a SIGPIPE.

    (As to why this doesn't happen on Linux et.al., I'd guess
    it's because 'cat' uses a larger buffer on those systems.
    It could also be timing-dependent).

     
  • Jeffrey Hobbs

    Jeffrey Hobbs - 2007-02-09

    Logged In: YES
    user_id=72656
    Originator: NO

    Works for me ...

    % info patch
    8.4.15
    % exec cat file1 | dd bs=1 count=530 of=file2 2>/dev/null
    child process exited abnormally
    % set errorInfo
    child process exited abnormally
    while executing
    "exec cat file1 | dd bs=1 count=530 of=file2 2>/dev/null"
    % set errorCode
    CHILDSTATUS 26296 2
    % uname -a
    HP-UX bertha B.11.00 U 9000/800 136901587 unlimited-user license

     
  • Jeffrey Hobbs

    Jeffrey Hobbs - 2007-02-09
    • status: open --> pending-works-for-me
     
  • SourceForge Robot

    Logged In: YES
    user_id=1312539
    Originator: NO

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 14 days (the time period specified by
    the administrator of this Tracker).

     
  • SourceForge Robot

    • status: pending-works-for-me --> closed-works-for-me
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks