possible memory corruption in tar

[Omer Woloch]

We have experienced the following problem when using gtar in our application:

Platform: Solaris 5.7 SPARC Ultra-250

 

gtar was executed through a subprocess that inherited a large fd table [190 entries occupied] from our main process. gtar exited with I/O error of unexplained nature. 

When tracing it with truss, I discovered that while it opens a file for output getting fd=193, when it tries to write, it actually writes to fd=122 which is occupied by the parent process.

Attached is the truss output. 

line 1236 output file created,

line 1339 write to wrong filedescriptor

 

thanks,

Omer   

 

 

Omer Woloch,
Software Developer,
mailto: address@hidden Tel: +972-3-7534718 

Check Point Software Technologies Ltd. http://www.checkpoint.com
=====================================================
This message may contain confidential and/or proprietary information, and
is intended only for the person/entity to whom it was originally addressed.
The content of this message may contain private views and opinions which do
not constitute a formal disclosure or commitment unless specifically stated.

 

 

tar.truss
Description: Binary data