Menu

#503 Update build script to build a debugger version and none debugging version of bochs or make debugging available as plugin

nice_to_have
closed
1
2024-12-18
2023-09-24
Oliver
No

I'm using Debian here where Bochs was compiled with debugging support. There is therefore no way to deactivate the debugger functions without recompiling Bochs yourself.

So I'm wondering why the build script doesn't just build two binaries. One with debugging support, you could call this "bochs-debug" and the other without debugging support, which is then simply called "bochs-bin".
This way you would have both versions of Bochs available and with a symbolic link called bochs you could then select the corresponding version when you need it by simply adapting the symbolic link or starting the corresponding file directly.

Of course you could say that it is the distribution's job to compile Bochs with two different build configurations, so that two binaries with and without debugging support are available. But the fact that this isn't done means that the maintainers either have too much to do with other packages themselves or that they don't care.
But if the standard build script of the Bochs project builds two Bochs binaries by default, then they are already there. Therefore this might be a better way to solve the problem.

But it would be even better if the debugging support could be loaded or unloaded at runtime as a plugin. But that doesn't seem to be possible at the moment. In any case, unloading iodebug with the "plugin_ctrl: iodebug=false" option did not disable the debugger. I still had to press the C key for continue when starting bochs, so the debugger was still active.

Discussion

  • Stanislav Shwartsman

    Bochs debugger will be enabled in main release now and can be used from the same binary with high performance version.

     
  • Stanislav Shwartsman

    • status: open --> closed
    • assigned_to: Stanislav Shwartsman
     

Log in to post a comment.

MongoDB Logo MongoDB