|
From: Satya V. G. <gup...@ne...> - 2010-06-08 09:27:17
|
I am using checkgrind on a system that has very little disk space. I am wondering if someone knows how I can direct the checkgrind output files (basic block, Function before, Function after) to a network socket instead? Thanks SVG ____________________________________________________________ Get Free Email with Video Mail & Video Chat! http://www.netzero.net/freeemail?refcd=NZTAGOUT1FREM0210 |
|
From: Fred S. <fs...@co...> - 2010-06-08 13:07:36
|
Satay: Have you looked at "nc" (netcat)? Fred Smith Senior Applications Programmer/Analyst Computrition, Inc. 175 Middlesex Turnpike Bedford, MA 01730 ph: 781-275-4488 x148 fax: 781-687-8884 From: Satya V. Gupta [mailto:gup...@ne...] Sent: Tuesday, June 08, 2010 5:26 AM To: val...@li... Subject: [Valgrind-users] Can data from checkgrind output files be directedto a network socket instead I am using checkgrind on a system that has very little disk space. I am wondering if someone knows how I can direct the checkgrind output files (basic block, Function before, Function after) to a network socket instead? Thanks SVG ____________________________________________________________ Get Free Email with Video Mail & Video Chat! <http://www.netzero.net/freeemail?refcd=NZTAGOUT1FREM0210> This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error please notify the system manager. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email |
|
From: John R. <jr...@bi...> - 2010-06-08 14:01:44
|
> how can I direct the checkgrind output files
> (basic block, Function before, Function after) to a network socket instead?
If checkgrind forces its output onto named files (instead of designated
but unnamed file descriptors), then create those filenames in advance
as named pipes using "mkfifo", then for each named pipe use a parallel
process (such as "cp" or "cat") to copy the named pipe to the socket.
File descriptors can be re-directed using shell syntax. As Fred Smith
suggested, the usual destination would be 'nc' (netcat).
nc is very versatile, but if for some reason it is not enough, then
write a small program to establish the socket, dup2(socket, 1),
and finally execve("checkgrind", ...) which will re-direct stdout
to the socket.
>From within any Linux process, file descriptor k may be referenced
as the filename /proc/self/fd/k. For instance, stderr is
"/proc/self/fd/2".
[All of this is no different for 'checkgrind' than for any process.]
--
|
|
From: Bart V. A. <bva...@ac...> - 2010-06-08 14:11:42
|
On Tue, Jun 8, 2010 at 11:25 AM, Satya V. Gupta <gup...@ne...>wrote: > I am using checkgrind on a system that has very little disk space. I am > wondering if someone knows how I can direct the checkgrind output files > (basic block, Function before, Function after) to a network socket instead? > The most convenient way to make sure that data is saved somewhere else is to use NFS. Just mount a directory via NFS from a server (e.g. on /mnt), change the current directory to /mnt and start checkgrind (what is checkgrind ?). Bart. |