This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: PLEASE HELP regarding System Tap
- From: "Khushboo Goel" <kgoel at usc dot edu>
- To: systemtap at sources dot redhat dot com
- Date: Mon, 7 Jul 2008 13:30:55 -0700
- Subject: Re: PLEASE HELP regarding System Tap
- References: <358a5c070807071002i28110b08p8c4213e72cc11386@mail.gmail.com> <20080707182856.GA7805@redhat.com>
>
> > I am using System Tap for probing kernel function so that I can know
> > more about packet that are send over network. For this I need to
> > open a File so that I can save all raw data. I want to save this
> > data when I probing in the function, continuously.
>
> We don't have a C stdio-like facility in systemtap yet. You can make
> your systemtap probe handler just printf(...), which will come out at
> the stap(run) command's stdout. You can redirect that as you like
> (perhaps using the "-o" option). Is that sufficient?
> ------
When i use -o option, it gives me buffer overflow error, i am
anyhow not printing anything on screen, i am using an aggregate
variable to store all information, but i have huge data around 50K
packets in one run ,which gives me overflow buffer , i also increased
the stack size but if i increase the number of packets i send over the
network, it gives me same error.
>
>
> > I using FILE *fp = NULL, to make file pointer, but its not allowing
> > to me do it.
>
> Right, that would be C code that's appropriate to run in a user-space
> program. Systemtap probe scripts resemble C, but not that much. Plus
> as any kernel-side code, they cannot just invoke user-space libraries
> like stdio.
>
>
> - FChE