tau_register_context_event(3) [debian man page]

TAU_REGISTER_CONTEXT(3) 				      TAU Instrumentation API					   TAU_REGISTER_CONTEXT(3)

NAME

       TAU_REGISTER_CONTEXT_EVENT - Registers a context event

SYNOPSIS

       C/C++:

       TAU_REGISTER_CONTEXT_EVENT(TauUserEvent variable, char *event_name);

       Fortran:

       TAU_REGISTER_CONTEXT_EVENT(int variable(2), character event_name(size));

DESCRIPTION

       Creates a context event with name. A context event appends the names of routines executing on the callstack to the name specified by the
       user. Whenver a context event is triggered, the callstack is examined to determine the context of execution. Starting from the parent
       function where the event is triggered, TAU walks up the callstack to a depth specified by the user in the environment variable
       TAU_CALLPATH_DEPTH. If this environment variable is not specified, TAU uses 2 as the default depth. For e.g., if the user registers a
       context event with the name "memory used" and specifies 3 as the callpath depth, and if the event is triggered in two locations (in routine
       a, when it was called by b, when it was called by c, and in routine h, when it was called by g, when it was called by i), then, we'd see
       the user defined event information for "memory used: c() => b() => a()" and "memory used: i() => g() => h()".

EXAMPLE

       C/C++ :

       int f2(void)
       {
	 static int count = 0;
	 count ++;
	 TAU_PROFILE("f2()", "(sleeps 2 sec, calls f3)", TAU_USER);
	 TAU_REGISTER_CONTEXT_EVENT(event, "Iteration count");
       /*
	 if (count == 2)
	   TAU_DISABLE_CONTEXT_EVENT(event);
       */
	 printf("Inside f2: sleeps 2 sec, calls f3
");

	 TAU_CONTEXT_EVENT(event, 232+count);
	 sleep(2);
	 f3();
	 return 0;
       }

       Fortran :

       subroutine foo(id)
	 integer id

	 integer profiler(2) / 0, 0 /
	 integer maev(2) / 0, 0 /
	 integer mdev(2) / 0, 0 /
	 save profiler, maev, mdev

	 integer :: ierr
	 integer :: h, t, u
	 INTEGER, ALLOCATABLE :: STORAGEARY(:)
	 DOUBLEPRECISION   edata

	 call TAU_PROFILE_TIMER(profiler, 'FOO')
	 call TAU_PROFILE_START(profiler)
	 call TAU_PROFILE_SET_NODE(0)

	 call TAU_REGISTER_CONTEXT_EVENT(maev, "STORAGEARY Alloc [cubes.f:20]")
	 call TAU_REGISTER_CONTEXT_EVENT(mdev, "STORAGEARY Dealloc [cubes.f:37]")

	 allocate(STORAGEARY(1:999), STAT=IERR)
	 edata = SIZE(STORAGEARY)*sizeof(INTEGER)
	 call TAU_CONTEXT_EVENT(maev, edata)
	 ...
	 deallocate(STORAGEARY)
	 edata = SIZE(STORAGEARY)*sizeof(INTEGER)
	 call TAU_CONTEXT_EVENT(mdev, edata)
	 call TAU_PROFILE_STOP(profiler)
	 end subroutine foo

SEE ALSO

       TAU_CONTEXT_EVENT(3), TAU_ENABLE_CONTEXT_EVENT(3), TAU_DISABLE_CONTEXT_EVENT(3), TAU_REGISTER_EVENT(3), TAU_REPORT_STATISTICS(3),
       TAU_REPORT_THREAD_STATISTICS(3), TAU_GET_EVENT_NAMES(3), TAU_GET_EVENT_VALS(3)

								    08/31/2005						   TAU_REGISTER_CONTEXT(3)

Check Out this Related Man Page

END(3)							     Linux Programmer's Manual							    END(3)

NAME

       etext, edata, end - end of program segments

SYNOPSIS

       extern etext;
       extern edata;
       extern end;

DESCRIPTION

       The addresses of these symbols indicate the end of various program segments:

       etext  This is the first address past the end of the text segment (the program code).

       edata  This is the first address past the end of the initialized data segment.

       end    This is the first address past the end of the uninitialized data segment (also known as the BSS segment).

CONFORMING TO

       Although these symbols have long been provided on most Unix systems, they are not standardized; use with caution.

NOTES

       The program must explicitly declare these symbols; they are not defined in any header file.

       On some systems the names of these symbols are preceded by underscores, thus: _etext, _edata, and _end.	These symbols are also defined for
       programs compiled on Linux.

       At the start of program execution, the program break will be somewhere near &end (perhaps at the start of the  following  page).   However,
       the  break  will  change as memory is allocated via brk(2) or malloc(3).  Use sbrk(2) with an argument of zero to find the current value of
       the program break.

EXAMPLE

       When run, the program below produces output such as the following:

	   $ ./a.out
	   First address past:
	       program text (etext)	  0x8048568
	       initialized data (edata)   0x804a01c
	       uninitialized data (end)   0x804a024

   Program source

       #include <stdio.h>
       #include <stdlib.h>

       extern char etext, edata, end; /* The symbols must have some type,
					  or "gcc -Wall" complains */

       int
       main(int argc, char *argv[])
       {
	   printf("First address past:
");
	   printf("    program text (etext)	 %10p
", &etext);
	   printf("    initialized data (edata)  %10p
", &edata);
	   printf("    uninitialized data (end)  %10p
", &end);

	   exit(EXIT_SUCCESS);
       }

SEE ALSO

       objdump(1), readelf(1), sbrk(2), elf(5)

COLOPHON

       This page is part of release 3.27 of the Linux man-pages project.  A description of the project, and information about reporting bugs,  can
       be found at http://www.kernel.org/doc/man-pages/.

GNU
								    2008-07-17								    END(3)

Linux and UNIX Man Pages

tau_register_context_event(3) [debian man page]

Check Out this Related Man Page