7.1.1.1. Reporting errors from Bochs compilation

When reporting errors while building Bochs to the bochs-developers mailing list or the SF bug tracker for the Bochs project, this information is required to fix the issue:

• host platorm / build environment

• Bochs release version or GIT SHA revision code

• configure options used

• full error message

• config.log output if configure failure

• source file name and line number if compile error

Before reporting us the issue, make sure that a similar one hasn't been already reported or someone created a patch to fix it. If you are familiar with C++ and you can write some code to fix your problem, you can post it in the bochs-developers mailing list or submit the patch in SF patch tracker for Bochs.

7.1.1.2. Reporting Bochs runtime issues

If Bochs does not work properly (e.g. panic, segfault, malfunction of emulated device) we need some information to find out what's going on:

• Bochs version used (version number if binary release / GIT revision if self-compiled)

• host platorm / build environment (if self-compiled)

• bochsrc options used

• error message (if panic or program termination)

• log file output (related section only if too big)

7.1.1.3. Submitting a patch for Bochs

Patches for Bochs should be provided in the "unified diff" format. In addition to the patch file and a detailed description this information is required:

• patch applies to Bochs release version / GIT revision

• test case (if required)

When you are are interested in writing a patch to fix bugs or add new features, you should have a look at the developer documentation. For some parts of the Bochs code we have already written some basic information.