[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 162848] New: --log-file output isn't split when a program forks
From:       Nicholas Nethercote <njn () cs ! utexas ! edu>
Date:       2008-05-29 23:26:41
Message-ID: 20080530012639.162848.njn () cs ! utexas ! edu
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=162848         
           Summary: --log-file output isn't split when a program forks
           Product: valgrind
           Version: 3.4 SVN
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: jseward acm org
        ReportedBy: njn cs utexas edu


If a program has PID=1 and is using --log-file=foo.%p, its logging output gets
written to "foo.1".  If it forks, then the child's logging output should start
going into a different file (eg. "foo.2") to the parent's logging output. 
Currently it doesn't.

Furthermore, if we implemented this, if the child then does an 'exec', the child
log file ("foo.2") will be overwritten by the newly exec'd process.  This
probably isn't a big deal, since the gap between fork and exec in a child is
typically very small, so there's not much potential for lost information.
[prev in list] [next in list] [prev in thread] [next in thread]