Fix for bug 162848: - --log-file output isn't split when a program forks

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Fix for bug 162848: - --log-file output isn't split when a program forks

iraisr
Dear developers,
Please kindly review proposed patch for bug 162848 [1]
and let me know your comments.
Kind regards,
I.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|

Re: Fix for bug 162848: - --log-file output isn't split when a program forks

Eliot Moss
On 12/29/2016 8:50 AM, Ivo Raisr wrote:
> Dear developers,
> Please kindly review proposed patch for bug 162848 [1]
> and let me know your comments.
> Kind regards,
> I.
>
> [1] https://bugs.kde.org/show_bug.cgi?id=162848

I had developed a patch some time ago that allows for a script to
be invoked to generate the log file name to be used for each fork.
Among other things, this allows for a fresh named pipe to be created
with a process at the other end to consume the output (for me,
typically gzip, to compress large traces).

AFAIK it is still pending because I did not provide a regression
test case (sigh).  Maybe this should be revived and I should create
a test case.  Let me know if you would like the patch posted here.

Regards - Eliot Moss

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers
Reply | Threaded
Open this post in threaded view
|

Re: Fix for bug 162848: - --log-file output isn't split when a program forks

John Reiser
On 12/29/2016 07:09 AM, Eliot Moss wrote:

> On 12/29/2016 8:50 AM, Ivo Raisr wrote:
>> Dear developers,
>> Please kindly review proposed patch for bug 162848 [1]
>> and let me know your comments.
>> Kind regards,
>> I.
>>
>> [1] https://bugs.kde.org/show_bug.cgi?id=162848
>
> I had developed a patch some time ago that allows for a script to
> be invoked to generate the log file name to be used for each fork.
> Among other things, this allows for a fresh named pipe to be created
> with a process at the other end to consume the output (for me,
> typically gzip, to compress large traces).
>
> AFAIK it is still pending because I did not provide a regression
> test case (sigh).  Maybe this should be revived and I should create
> a test case.  Let me know if you would like the patch posted here.

Post it as an attachment to some bug report: your own, or Ivo's bug report above.


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-developers mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/valgrind-developers