"Fossies" - the Fresh Open Source Software Archive

Member "ettercap-0.8.3.1/README.BUGS" (1 Aug 2020, 3965 Bytes) of package /linux/privat/ettercap-0.8.3.1.tar.gz:

As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file. See also the latest Fossies "Diffs" side-by-side code changes report for "README.BUGS": 0.8.3_vs_0.8.3.1.

    1 ==============================================================================
    2 ==============================================================================
    3 
    4 
    5        @@@@@@@ @@@@@@@ @@@@@@@ @@@@@@@ @@@@@@@ @@@@@@@ @@@@@@@ @@@@@@@
    6        @@        @@@     @@@   @@      @@   @@ @@      @@   @@ @@   @@
    7        @@@@@@    @@@     @@@   @@@@@@  @@@@@@  @@      @@@@@@@ @@@@@@
    8        @@        @@@     @@@   @@      @@  @@  @@      @@   @@ @@
    9        @@@@@@@   @@@     @@@   @@@@@@@ @@  @@@ @@@@@@@ @@   @@ @@     NG
   10 
   11                       Copyright 2001-2013 The Ettercap Dev Team
   12 
   13 ==============================================================================
   14 ==============================================================================
   15 
   16 "Debugging is twice as hard as writing the code in the first place.
   17 Therefore, if you write the code as cleverly as possible, you are,
   18 by definition, not smart enough to debug it." - Brian W. Kernighan
   19 
   20 
   21 If you found a new bug please report it to
   22 https://github.com/Ettercap/ettercap/issues or by sending an email to
   23 <ettercap-users@lists.ettercap-project.org>
   24 
   25 
   26 ==============================================================================
   27                      C O M P I L E  T I M E    B U G S
   28 ==============================================================================
   29 
   30 If you are not able to compile ettercap on your system, please make a bug
   31 report. In order to help you fix the problem we need the following
   32 information:
   33 
   34 1) a description of your operating system (including any patch level)
   35 
   36    # uname -a > os.log
   37 
   38 2) the cmake cache file
   39 
   40    # cat CMakeCache.txt
   41 
   42 3) the entire output from 'make'
   43 
   44    # make 1> make_output 2> make_error 
   45 
   46 4) make a tarball with all the needed infos
   47    
   48    # tar pczf compile_error.tar.gz os.log \
   49                                    CMakeCache.txt \
   50                                    make_output \
   51                                    make_error
   52 
   53 ==============================================================================
   54                            R U N T I M E    B U G S
   55 ==============================================================================
   56 
   57 
   58 If the bug is critical and results in a segmentation fault follow these steps
   59 to make a detailed bug report in order to help us to find the bug and fix it.
   60 
   61 1) recompile the program in debug mode:
   62 
   63   (follow the instructions on README.GIT file in order to pull the repository and build the program in debug mode)
   64 
   65 
   66 2) force ettercap to not drop privileges to make sure the core is dumped:
   67 
   68    # export EC_UID=0
   69    # export EC_GID=0
   70 
   71 
   72 3) override any limit for coredumps:
   73 
   74    # ulimit -c unlimited
   75 
   76 
   77 4) enable memory checks (if your system supports them), so the program will
   78    abort if some heap corruption is in place:
   79 
   80    # export MALLOC_CHECK_=2
   81    
   82 
   83 5) dump to a file the traffic that causes the crash (we need it to reproduce
   84     the situation)
   85 
   86    # ./src/ettercap -w offending_packets.pcap ... --your-options-here ...
   87 
   88 
   89 6) analyze the core with gdb and send us the backtrace:
   90 
   91    # gdb ettercap core
   92    
   93    (gdb) bt
   94    (gdb) quit
   95 
   96    copy and paste the output of the gdb command 'bt' in a file (backtrace.log)
   97 
   98 6a) if you don't get a core (for any reason), you can run ettercap within gdb:
   99 
  100    # gdb ettercap
  101    
  102    (gdb) r your_parameters_here
  103 
  104    when it catches the segfault, you can get the backtrace with the 'bt'
  105    command
  106 
  107 
  108 7) collect useful information about your network:
  109 
  110    # ifconfig -a > network.txt
  111    # arp -an >> network.txt
  112    # netstat -rn >> network.txt
  113    
  114 
  115 8) tar all the information together with the log generated by ettercap:
  116 
  117    # tar zcvf bugreport.tar.gz ettercap-*-debug.log \
  118                                offending_packets.pcap \
  119                                network.txt \
  120                                backtrace.log
  121 
  122 
  123 9) mail the tarball to us with a brief description of the bug.
  124 
  125 =============================================================================
  126 
  127 vim:ts=3:expandtab
  128