public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: hunt@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: src/runtime ChangeLog map-gen.c map.c pmap-gen ...
Date: Wed, 27 Feb 2008 19:45:00 -0000	[thread overview]
Message-ID: <20080227194546.5505.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/systemtap
Module name:	src
Changes by:	hunt@sourceware.org	2008-02-27 19:45:46

Modified files:
	runtime        : ChangeLog map-gen.c map.c pmap-gen.c runtime.h 
	                 sym.c sym.h 
	runtime/staprun: symbols.c 
	runtime/transport: ChangeLog control.c procfs.c symbols.c 
	                   transport.c transport_msgs.h 
Added files:
	runtime        : debug.h mempool.c 

Log message:
	2008-02-27  Martin Hunt  <hunt@redhat.com>
	
	* sym.h (_stp_module): Add text_size, lock, and unwind data
	pointer.
	* sym.c (_stp_find_module_by_addr): New function.
	(_stp_kallsyms_lookup): Call _stp_find_module_by_addr().
	(_stp_get_unwind_info): New.
	
	* runtime.h: Move debug macros to debug.h. Include it.
	* debug.h: New file.
	* map.c: Update debug calls.
	* map-gen.c: Update debug calls.
	* pmap-gen.c: Update debug calls.
	
	* mempool.c: New file.
	
	* symbols.c: Use rwlocks. Use new dbug macros. Handle
	unwind info if present.
	
	* transport.c: Include mempool.c. Update dbug and kbug calls
	to new macros.
	* transport_msgs.h (_stp_command_name): Add
	struct containing message names for debugging.
	
	* control.c, procfs.c: Use new dbug macros. Use
	new mempool functions.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/debug.h.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/mempool.c.diff?cvsroot=systemtap&r1=NONE&r2=1.1
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/ChangeLog.diff?cvsroot=systemtap&r1=1.243&r2=1.244
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/map-gen.c.diff?cvsroot=systemtap&r1=1.11&r2=1.12
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/map.c.diff?cvsroot=systemtap&r1=1.43&r2=1.44
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/pmap-gen.c.diff?cvsroot=systemtap&r1=1.13&r2=1.14
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/runtime.h.diff?cvsroot=systemtap&r1=1.43&r2=1.44
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/sym.c.diff?cvsroot=systemtap&r1=1.22&r2=1.23
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/sym.h.diff?cvsroot=systemtap&r1=1.5&r2=1.6
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/staprun/symbols.c.diff?cvsroot=systemtap&r1=1.11&r2=1.12
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/ChangeLog.diff?cvsroot=systemtap&r1=1.82&r2=1.83
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/control.c.diff?cvsroot=systemtap&r1=1.21&r2=1.22
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/procfs.c.diff?cvsroot=systemtap&r1=1.39&r2=1.40
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/symbols.c.diff?cvsroot=systemtap&r1=1.18&r2=1.19
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/transport.c.diff?cvsroot=systemtap&r1=1.49&r2=1.50
http://sourceware.org/cgi-bin/cvsweb.cgi/src/runtime/transport/transport_msgs.h.diff?cvsroot=systemtap&r1=1.12&r2=1.13


                 reply	other threads:[~2008-02-27 19:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080227194546.5505.qmail@sourceware.org \
    --to=hunt@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).