Menu

Tree [r9] /
 History

HTTPS access


File Date Author Commit
 cb_analyze_dep 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 cb_files 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 cb_meta 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 cb_meta_merge 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 cb_remove_from_source 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 cb_strace_to_xml 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 helper 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 lib 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 scripts 2009-05-12 Somewherehere [r8] strace parameters changed
 share 2012-07-04 somewherehere [r9] Mail address changed
 Makefile 2009-01-21 somewherehere [r7] Make it compile with g++ too.
 changelog.txt 2009-05-12 Somewherehere [r8] strace parameters changed
 createSrcRelease.sh 2008-12-22 Somewherehere [r5] Buxfixes, a script and version 0.8.6 release
 createdir.sh 2008-12-10 somewherehere [r3] Libs (reduced to the basic needs) added
 export.sh 2008-12-06 somewherehere [r2] Uploading all self written source files, but ex...
 gpl-license.txt 2008-12-06 somewherehere [r2] Uploading all self written source files, but ex...
 readme.txt 2012-07-04 somewherehere [r9] Mail address changed

Read Me

------------ This version is from the SVN trunk, please use an official release instead-----
(c) 2008 by Malte Marwedel m DOT talk AT marwedels DOT de
COPYBIRDS, Copy binaries runtime data surrounding
http://copybirds.sourceforge.net
Terms of Use: GPL Version 2 or later

============ Howto compile ===============================
On a fresh Kubuntu 7.04 (Ubuntu 8.10 too) Live-CD the following three packages and its dependencies have to be installed before compiling works:
libc6-dev, libxml2-dev, freeglut3-dev

run
  make
in this directory.

After compiling, make the content of bin available in your $PATH variable
This may work with:
  PATH=$PATH:PATHTOTHEBINDIRECTORY
  export PATH

============ Quickstart ==================================
Go into a writeable directory. Here you may run (no root rights needed)
  cb_automatic.sh <your program to capture with parameters>
And follow the instructions.

Then, on the target system, you may run: (You will be asked about your sudo password, which means you have to be in the sudoers file.)
  ./WHATEVERYOUNAMEIT.sh

You need more help?
Every program and script supports
  -h
as parameter to print instructions. (And -help, --help too if you prefer this)

=========== What are all those different programs for? ===
cb_analyze_dep: .deb package dependency analysis
cb_files: Copies files together in one directory
cb_automatic.sh: Interactive script, calls cb_trace_program.sh and cb_make_selfextracting.sh
cb_make_selfextracting.sh: Generates the self extracting archive with all files, calls cb_files
cb_meta_check: Gathers and compares meta informations
cb_meta_merge: Unifies meta information from multiple xml files into one file
cb_remove_from_source: Deletes files on the target system if a self-extracting archive is unpacked (be very careful if you run this on productive systems)
cb_strace_to_xml: Converts the output of strace to a suitable xml representation
cb_trace_program.sh: Calls strace, cb_strace_to_xml and cb_meta_check with proper parameters

=========== Versions ===================================
Please read changelog.txt to see the current version number.
Note: Odd versions will be the current code from the SVN between releases. Even versions will be releases.
Example: 0.8.6: Is a release, 0.8.7 is the current developer code in the SVN which will end in the next release 0.8.8

=========== Troubleshooting on special machines ==========
The programs use escape sequences to generate color output in the console.
If you get problems with them, go to the file share/tools.h and define the preprocessor variable NOCOLOR. After doing so, please re-compile.
http://linuxgazette.net/issue65/padala.html

=========== Other things =================================
If you found a bug (especially crashes), please report.
You can trace crashes down by running the individual program with the gdb debugger:
1. Start the debugger:
  gdb cb_THE_PROGRAM_WHICH_CRASHED
2. Start the program within the debugger
  run THE_PARAMETERS_YOU_GAVE_THE_PROGRAM_AT_THE_CRASH
3. Wait for the crash and look where it happened:
  backtrace full
then mail me the whole output of gdb or report as a bug on sourceforge.
4. Exit the debugger
  q

Have fun.