Changes between Version 1 and Version 2 of TesterDocumentation


Ignore:
Timestamp:
04/23/10 10:50:54 (14 years ago)
Author:
Samuli Seppänen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TesterDocumentation

    v1 v2  
    1313 * If you have not cloned the git repository:
    1414
     15 {{{
    1516 git clone git://openvpn.git.sourceforge.net/gitroot/openvpn/openvpn-testing.git
    1617 cd openvpn-testing
    1718 git checkout -b allmerged origin/allmerged
     19 }}}
    1820
    1921 * If you already have git repository clone:
    2022
     23 {{{
    2124 cd openvpn-testing
    2225 git checkout allmerged
    2326 git pull --rebase origin
     27 }}}
    2428
    2529 * Prepare for building:
    2630 
     31 {{{
    2732 autoreconf -vi
     33 }}}
    2834
    2935 = Building OpenVPN testing from snapshots =
    3036
    3137 * Download the latest snapshot tarball from: ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/
    32 
    3338 * Unpack it
    3439
     40 {{{
    3541 gzip -dc openvpn-YYYYWW.tar.gz | tar xvf -
    3642 cd openvpn-devel/
     43 }}}
    3744
    3845 == Configure and compile ==
     
    4653Example:
    4754
     55 {{{
    4856 ./configure --disable-depr-random-resolv
    4957 make [-j <num CPU cores + 1>]
     58 }}}
    5059
    5160When testing this version, please give us a report to '''**TBD**'''.  This report should also include the output of:
    5261
     62 {{{
    5363 openvpn --version
     64 }}}
    5465
    5566in addition to the ./configure line use used for the compilation and all the configuration files you used.  We would like to have both success and fail reports.
     
    5970If OpenVPN crashes, you can help developers figure out the problem by giving them a backtrace of the crash. If you're running released (stable) version of OpenVPN, you should install the ''openvpn debug'' and ''gdb'' packages and then run openvpn via gdb. On "testing" turn on debugging before compilation. In either case you can get a backtrace of the crash like this:
    6071
     72 {{{
    6173 $ gdb /usr/sbin/openvpn
    6274 [gdb info message...blablabla...]
     
    6577 (gdb) bt
    6678 [full backtrace should appear]
     79 }}}
    6780
    6881 = Enable core dump =
     
    7083In some cases, it's not possible to trigger the bug when running via gdb directly.  In this case, you can enable core dumps.  On most distributions and *nix OSes today, you need to enable this from your shell before starting OpenVPN.
    7184
     85  {{{
    7286  $ ulimit -c unlimited
    73  
     87  }}}
    7488Then run OpenVPN with the normal arguments.  When OpenVPN crashes, it will now most likely create a core file which can be used for debugging the state of OpenVPN when it crashed.
    7589
     90  {{{
    7691  $ gdb openvpn {core file}
    7792  [gdb info message...blablabla...]
    7893  (gdb) bt
    7994  [full backtrace should appear]
     95  }}}
    8096
    8197Please save the core files for a little while before deleting them.  It might be that the developers would ask for a copy of the core file in some situations, to investigate more carefully the state OpenVPN was in when it crashed.  But be also aware of that these core files can (will most likely) contain sensitive data, like encryption keys and certificates.  So share with care.