public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: hunt@sourceware.org To: systemtap-cvs@sources.redhat.com Subject: src/tapset ChangeLog aux_syscalls.stp syscalls ... Date: Tue, 14 Feb 2006 09:03:00 -0000 [thread overview] Message-ID: <20060214090316.30684.qmail@sourceware.org> (raw) CVSROOT: /cvs/systemtap Module name: src Changes by: hunt@sourceware.org 2006-02-14 09:03:16 Modified files: tapset : ChangeLog aux_syscalls.stp syscalls.stp syscalls2.stp Log message: 2006-02-14 Martin Hunt <hunt@redhat.com> * aux_syscalls.stp (_struct_timeval_u): New function. (_struct_timeval): New function. (_struct_timespec_u): New function. (_struct_timespec): New function. (_struct_itimerval_u): New function: (_struct_itimerval): New function: (_signal_name): New function. (_module_flags_str): Fixed. * syscalls2.stp (syscall.setitimer): Use new function _struct_itimerval_u(). * syscalls.stp: Latest version. Many changes. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/tapset/ChangeLog.diff?cvsroot=systemtap&r1=1.6&r2=1.7 http://sourceware.org/cgi-bin/cvsweb.cgi/src/tapset/aux_syscalls.stp.diff?cvsroot=systemtap&r1=1.5&r2=1.6 http://sourceware.org/cgi-bin/cvsweb.cgi/src/tapset/syscalls.stp.diff?cvsroot=systemtap&r1=1.3&r2=1.4 http://sourceware.org/cgi-bin/cvsweb.cgi/src/tapset/syscalls2.stp.diff?cvsroot=systemtap&r1=1.7&r2=1.8
next reply other threads:[~2006-02-14 9:03 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-14 9:03 hunt [this message] 2006-05-30 20:25 hunt 2007-06-07 15:11 hunt 2007-07-03 21:43 hunt 2007-07-10 18:30 hunt 2007-07-16 17:18 hunt 2007-07-31 16:20 hunt 2007-08-15 19:17 hunt 2007-08-16 12:55 hunt 2007-08-22 15:12 hunt 2007-08-22 20:41 hunt 2007-08-23 13:05 hunt 2007-09-24 14:19 hunt 2007-10-05 17:56 hunt 2007-10-09 13:28 hunt
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=20060214090316.30684.qmail@sourceware.org \ --to=hunt@sourceware.org \ --cc=systemtap-cvs@sources.redhat.com \ /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: linkBe 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).