Changes between Version 1 and Version 2 of TesterDocumentation
- Timestamp:
- 04/23/10 10:50:54 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TesterDocumentation
v1 v2 13 13 * If you have not cloned the git repository: 14 14 15 {{{ 15 16 git clone git://openvpn.git.sourceforge.net/gitroot/openvpn/openvpn-testing.git 16 17 cd openvpn-testing 17 18 git checkout -b allmerged origin/allmerged 19 }}} 18 20 19 21 * If you already have git repository clone: 20 22 23 {{{ 21 24 cd openvpn-testing 22 25 git checkout allmerged 23 26 git pull --rebase origin 27 }}} 24 28 25 29 * Prepare for building: 26 30 31 {{{ 27 32 autoreconf -vi 33 }}} 28 34 29 35 = Building OpenVPN testing from snapshots = 30 36 31 37 * Download the latest snapshot tarball from: ftp://ftp.secure-computing.net/pub/FreeBSD/ports/openvpn-devel/ 32 33 38 * Unpack it 34 39 40 {{{ 35 41 gzip -dc openvpn-YYYYWW.tar.gz | tar xvf - 36 42 cd openvpn-devel/ 43 }}} 37 44 38 45 == Configure and compile == … … 46 53 Example: 47 54 55 {{{ 48 56 ./configure --disable-depr-random-resolv 49 57 make [-j <num CPU cores + 1>] 58 }}} 50 59 51 60 When testing this version, please give us a report to '''**TBD**'''. This report should also include the output of: 52 61 62 {{{ 53 63 openvpn --version 64 }}} 54 65 55 66 in 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. … … 59 70 If 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: 60 71 72 {{{ 61 73 $ gdb /usr/sbin/openvpn 62 74 [gdb info message...blablabla...] … … 65 77 (gdb) bt 66 78 [full backtrace should appear] 79 }}} 67 80 68 81 = Enable core dump = … … 70 83 In 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. 71 84 85 {{{ 72 86 $ ulimit -c unlimited 73 87 }}} 74 88 Then 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. 75 89 90 {{{ 76 91 $ gdb openvpn {core file} 77 92 [gdb info message...blablabla...] 78 93 (gdb) bt 79 94 [full backtrace should appear] 95 }}} 80 96 81 97 Please 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.