From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: _valgrind v1.0.0
Date: Sun, 18 Aug 2002 18:27:51 -0700 (PDT) [thread overview]
Message-ID: <20020819012752.19286.qmail@web10403.mail.yahoo.com> (raw)
This patch is for the valgrind completion function. Version 1.0.0 of Valgrind
was recently released.
-FR.
Index: _valgrind
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_valgrind,v
retrieving revision 1.1
diff -u -r1.1 _valgrind
--- _valgrind 20 May 2002 21:52:02 -0000 1.1
+++ _valgrind 19 Aug 2002 01:24:38 -0000
@@ -5,44 +5,53 @@
# Post-handedits
# For details see:
# http://www.geocities.com/f_rosencrantz/xml_completion.htm
+#
+# This is for valgrind version: 1.0.0
+# Valgrind URL: http://developer.kde.org/~sewardj/
local context state line
typeset -A opt_args
-_arguments \
- '--help[show this message]' \
- '--version[show version]' \
- '(--quiet)-q[run silently; only print error msgs]' \
- '(-q)--quiet[run silently; only print error msgs]' \
- '(--verbose)-v[be more verbose, incl counts of errors]' \
- '(-v)--verbose[be more verbose, incl counts of errors]' \
- '--gdb-attach=-:start GDB when errors detected? [no]:(no yes)' \
- '--demangle=-:automatically demangle C++ names? [yes]:(no yes)' \
- '--num-callers=-:show <num> callers in stack traces [4]:' \
- '--partial-loads-ok=-:too hard to explain here; see manual [yes]:(no yes)' \
- '--leak-check=-:search for memory leaks at exit? [no]:(no yes)' \
- '--leak-resolution=-:amount of bt merging in leak check [low]:(low med high)'
\
- '--show-reachable=-:show reachable blocks in leak check? [no]:(no yes)' \
- '--sloppy-malloc=-:round malloc sizes to next word? [no]:(no yes)' \
- '--trace-children=-:Valgrind-ise child processes? [no]:(no yes)' \
- '--logfile-fd=-:file descriptor for messages [2=stderr]:_file_descriptors' \
- '--freelist-vol=-:volume of freed blocks queue [1000000]:' \
- '--workaround-gcc296-bugs=-:self explanatory [no]:(no yes)' \
- '--suppressions=-:suppress errors described in suppressions file
<filename>:_files' \
- '--client-perms=-:handle client VG_MAKE_* requests? [no]:(no yes)' \
- "--check-addrVs=-:experimental lighterweight checking? [yes] yes ==
Valgrind's original behaviour:(no yes)" \
- '--sanity-level=-:level of sanity checking to do [1]:' \
- '--single-step=-:translate each instr separately? [no]:(no yes)' \
- '--optimise=-:improve intermediate code? [yes]:(no yes)' \
- '--instrument=-:actually do memory checks? [yes]:(no yes)' \
- '--cleanup=-:improve after instrumentation? [yes]:(no yes)' \
- '--trace-syscalls=-:show all system calls? [no]:(no yes)' \
- '--trace-signals=-:show signal handling details? [no]:(no yes)' \
- '--trace-symtab=-:show symbol table details? [no]:(no yes)' \
- '--trace-malloc=-:show client malloc details? [no]:(no yes)' \
- '--trace-sched=-:show thread scheduler details? [no]:(no yes)' \
- '--trace-pthread=-:show pthread event details? [no]:(no yes)' \
- '--stop-after=-:switch to real CPU after executing <number> basic blocks
[infinity]:' \
- "--dump-error=-:show translation for basic block associated with <number>'th
error context [0=don't show any]:" \
- '1:Command name:_command_names -e' \
- '*::Args :_normal' \
- && return 0
+ _arguments \
+ '--help[show this message]' \
+ '--version[show version]' \
+ '(--quiet)-q[run silently; only print error msgs]' \
+ '(-q)--quiet[run silently; only print error msgs]' \
+ '(--verbose)-v[be more verbose, incl counts of errors]' \
+ '(-v)--verbose[be more verbose, incl counts of errors]' \
+ '--gdb-attach=-:start GDB when errors detected? [no]:(no yes)' \
+ '--demangle=-:automatically demangle C++ names? [yes]:(no yes)' \
+ '--num-callers=-:show <num> callers in stack traces [4]:' \
+ '--error-limit=-:stop showing new errors if too many? [yes]:(no yes)' \
+ '--partial-loads-ok=-:too hard to explain here; see manual [yes]:(no yes)'
\
+ '--leak-check=-:search for memory leaks at exit? [no]:(no yes)' \
+ '--leak-resolution=-:amount of bt merging in leak check [low]:(low med
high)' \
+ '--show-reachable=-:show reachable blocks in leak check? [no]:(no yes)' \
+ '--sloppy-malloc=-:round malloc sizes to next word? [no]:(no yes)' \
+ '--alignment=-:set minimum alignment of allocations [4]:' \
+ '--trace-children=-:Valgrind-ise child processes? [no]:(no yes)' \
+ '--logfile-fd=-:file descriptor for messages [2=stderr]:_file_descriptors'
\
+ '--freelist-vol=-:volume of freed blocks queue [1000000]:' \
+ '--workaround-gcc296-bugs=-:self explanatory [no]:(no yes)' \
+ '--suppressions=-:suppress errors described in suppressions file
<filename>:_files' \
+ '--check-addrVs=-:experimental lighterweight checking? [yes]:(no yes)' \
+ '--cachesim=-:do cache profiling? [no]:(no yes)' \
+ '--I1=-:set I1 cache manually(size,assoc,line_size):' \
+ '--D1=-:set D1 cache manually(size,assoc,line_size):' \
+ '--L2=-:set L2 cache manually(size,assoc,line_size):' \
+ '--weird-hacks=-:Weird Hacks (comma separated)[no hacks
selected]:(ioctl-VTIME truncate-writes)' \
+ '--sanity-level=-:level of sanity checking to do [1]:' \
+ '--single-step=-:translate each instr separately? [no]:(no yes)' \
+ '--optimise=-:improve intermediate code? [yes]:(no yes)' \
+ '--instrument=-:actually do memory checks? [yes]:(no yes)' \
+ '--cleanup=-:improve after instrumentation? [yes]:(no yes)' \
+ '--smc-check=-:check writes for s-m-c? [some]:(none some all)' \
+ '--trace-syscalls=-:show all system calls? [no]:(no yes)' \
+ '--trace-signals=-:show signal handling details? [no]:(no yes)' \
+ '--trace-symtab=-:show symbol table details? [no]:(no yes)' \
+ '--trace-malloc=-:show client malloc details? [no]:(no yes)' \
+ '--trace-sched=-:show thread scheduler details? [no]:(no yes)' \
+ '--trace-pthread=-:show pthread event details? [none]:(none some all)' \
+ '--stop-after=-:switch to real CPU after executing <number> basic blocks
[infinity]:' \
+ "--dump-error=-:show translation for basic block associated with
<number>'th error context [0=don't show any]:" \
+ '1:Command name:_command_names -e' \
+ '*::Args :_normal' && return 0
__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
reply other threads:[~2002-08-19 1:51 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=20020819012752.19286.qmail@web10403.mail.yahoo.com \
--to=f_rosencrantz@yahoo.com \
--cc=zsh-workers@sunsite.auc.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).