Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
stracify
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nik | Klampfradler
stracify
Commits
e8ebbf33
Verified
Commit
e8ebbf33
authored
7 years ago
by
Dominik George
Browse files
Options
Downloads
Patches
Plain Diff
Add licence and readme.
parent
b9b36f48
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
LICENCE
+19
-0
19 additions, 0 deletions
LICENCE
README.md
+51
-0
51 additions, 0 deletions
README.md
with
70 additions
and
0 deletions
LICENCE
0 → 100644
+
19
−
0
View file @
e8ebbf33
Copyright 2017 Dominik George <d.george@tarent.de>
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to
deal in the Software without restriction, including without limitation the
rights to use, copy, modify, merge, publish, distribute, sublicense, and/or
sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
DEALINGS IN THE SOFTWARE.
This diff is collapsed.
Click to expand it.
README.md
0 → 100644
+
51
−
0
View file @
e8ebbf33
Universal strace wrapper for debugging
======================================
stracify is a universal strace wrapper for debugging purposes. It replaces
an arbitrary binary with itself, ensuring it will be called as close to the
original as possible, and also includes some management code to wrap or
unwrap binaries.
Installation
============
Install mksh as a dependency, then install the stracify script into the
PATH.
Wrapping a binary
=================
Wrapping a binary is done using the command
`sudo stracify /usr/bin/foo`
.
An optional strace filter expression can be passed, like
`sudo stracify
/usr/bin/foo open,write`
.
On Debian systems, care is taken to register the diversion with dpkg.
Finding the strace output of calls
==================================
The output fiels are stored in a directory structure organised like this:
```
/var/log/stracify/
|- usr_bin_foo/
|- root/
|- strace_2017-09-08T14:19:57+02:00_11911.log.11924
|- user1/
|- ...
```
This structure was chosen so all users can run the wrapped binary, but
without opening up the strace outputs from one user's calls to others. The
template for the log file names is
`strace_$date_$pif.$childpid`
.
Please note that due to the architecture of stracify, the logs will contain
quite a bit of trace from stracify and mksh themselves. This is not very
pretty, but better than losing functionality in the wrapped binary due to a
crooked call.
Unwrapping a binary
===================
A binary can be unwrapped using the command
`stracify unwrap /usr/bin/foo`
.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment