SourceForge Logo

Go to the SourceForge project home page








HeavyMole for testers

Go to documentation index

Table of contents

A. Things to test

As we already said, this release is essentially for testing purposes. Indeed it was never tested on a large scale and it may still have some problems. So, you can help us already by installing and using it, and by reporting bugs.

If you really want to help, you can also test separately the different modules of the application: in each library are a number of test programs for important classes. See Test programs for a complete listing and instructions on how to build and use them.

You can use the debug tools developped for heavymole...

Below are listed some critical low-level modules (see Architecture) that need to be extensively tested since the whole application relies on them:

  • the heavymole communication protocol (LibHMCP)
  • the heavymole file transfer protocol (LibHMFTP)
  • semi-reliable UDP (LibUDP)
  • servers and connections with servers (LibHMD & hmd)

B. Known bugs and problems

  • HeavyMole doesn't work under UNIX if you are not the super-user
  • the drop to another program under win32 doesn't work at present time, as it is not yet implemented in the win32 port of GTK+. It also doesn't work from the Explorer frame.
  • fonts and colors for the appearance in the preferences are not set
  • in the Transfer frame, the nice progress bar associated with download states has been disabled under MS Windows because it generates problems.
  • directory links do not work under win32
  • under MS Windows, the command line options don't print anything
  • under MS Windows, sometimes a DOS terminal appears displaying errors. These are bugs, please report them
  • you can't reuse a user created with a previous version of HeavyMole
  • it is not stable if compiled with gcc 2.96 and earlier
  • the stack-smashing attacks protector used in OpenBSD crashes the hmd server

C. Reporting bugs

You can report bugs at with a description of the bug and how we can reproduce it.

You can also use the redirection of heavymole or the debug.log file created by the debugframe, once you are sure it is relevant. You do not need to send us all the file since it may grow consequentially. Please consider that we have a mail box with 10 Mb of disk space!

We also invite you to use the Bug Tracker tool and the forum on the SourceForge project home page

D. Building HeavyMole for testing

First, we suggest you to download one of the tarballs, even if you already installed a HeavyMole RPM on your system, so you can work on a local copy with local data (the "heavymole.cfg" file in the "heavymole-x" directory points to local files in the "data" directory).

If you want, you can try a "configure" to see if everything is alright and then go and work in the "src" directory.

You can compile in different ways (see Debug Tools for details on debug options):

  • make: compiles the code without using the debug options.
  • make debug: compiles the code using the debug options.
  • make tests: compiles all the test programs without using the debug options.
  • make debugtests: compiles all the test programs using the debug options.

Each of these commands can be launched from each library directory to compile uniquely that library. If launched from the "src" or the main directory, "make" will create an executable file "heavymole" in the main directory. Don't forget to launch HeavyMole with "./heavymole" if you already have installed HeavyMole elsewhere in your PATH.

Under MS Windows, there is only one command available:
  • makealldebug.bat (only in root directory): compiles heavymole and debugframe using the debug options.

Compiling with debug options will do the following:

  • in most files: displays debug messages (see Debug MACROS)
  • HM_GUI: compiles the debugframe executable (see The debug frame)
  • allows performing search only on hosted files
  • LibHMTCP/; LibHMFTP/ "usleep" to slow down downloading and listing directories
  • LibHMCP: speed up update of usertable and hosted filetrees
  • a new menu entry will appear with IP data when you right-click on a user

So, if you want to use the application for test or development purposes, you'd better begin with a "make debug"... - This page was last updated on November, 26th 2003