probe_filter.c File Reference

#include <ctype.h>
#include <regex.h>
#include "log.h"
#include "dwdebug.h"
#include "dwdebug_priv.h"
#include "target_api.h"
#include "target.h"
#include "target_os.h"
#include "probe.h"
#include "probe_api.h"
#include "glib_wrapper.h"

Include dependency graph for probe_filter.c:

Go to the source code of this file.

Functions
int	probe_filter_check (struct probe *probe, tid_t tid, struct probe *trigger, int whence)
struct probe *	probe_create_filtered (struct target *target, tid_t tid, struct probe_ops *pops, const char *name, probe_handler_t pre_handler, struct target_nv_filter *pre_filter, probe_handler_t post_handler, struct target_nv_filter *post_filter, struct target_nv_filter *thread_filter, void *handler_data, int autofree, int tracked)

Function Documentation

struct probe* probe_create_filtered	(	struct target *	target,
		tid_t	tid,
		struct probe_ops *	pops,
		const char *	name,
		probe_handler_t	pre_handler,
		struct target_nv_filter *	pre_filter,
		probe_handler_t	post_handler,
		struct target_nv_filter *	post_filter,
		struct target_nv_filter *	thread_filter,
		void *	handler_data,
		int	autofree,
		int	tracked
	)

Probe Filter functions. If you attach a filter probe to a value probe, it uses the value probe as a source, and each time its pre/posthandlers are called, compares the named values to the filter value expressions, and fires the pre/post handlers if there is a match.

Filter probes should also have a notion of context, but they don't really have that yet. The only context initially is – if you set it to TID_GLOBAL, you'll get everything; otherwise, your filter won't be checked unless the probe event happened in .

Definition at line 95 of file probe_filter.c.

int probe_filter_check	(	struct probe *	probe,
		tid_t	tid,
		struct probe *	trigger,
		int	whence
	)

Definition at line 35 of file probe_filter.c.