Bochs 2.4.2 bugfix+ release

[stlw]

Bochs 2.4.2 was released Nov, 12.

Version 2.4.2 is a bugfix release. Here is the summary of changes :
- CPU and internal debugger

• VMX: implemented TPR shadow VMEXIT
  - Bugfixes for CPU emulation correctness (mostly for VMX support).
  - Bugfixes and updates for Bochs internal debugger
  • - On SMP system stepN command now affects only current processor

- Memory modelling

• - Bugfixes for > 32-bit physical address space.
  - Allow to emulate more physical memory than host actually could or would like to allocate.

- I/O Devices Bugfixes

• - Bugfixes for 8254 PIT, VGA, Cirrus-Logic SVGA, USB UCHI

- Cleanup configure options

• - Many configure options are deprecated and determined automatically from the others

You are welcome to download from sf.net Bochs webpage!

Stanislav

[01000101]

Excellent! Even though I usually download from the CVS, I always love seeing new BOCHS releases. Great job!

[AndreaOrru]

Thanks for your work, Bochs is just essential!

[qw]

Thanks for the update. I was still using 2.3.7.

EDIT: Hey, that new Start Menu is great!

Roel

[jal]

Great work, thanks!


JAL

[IanSeyler]

Is the "Bochs Enhanced Debugger" no longer included with the official distribution? I am using 2.3.7 since the config line below still works.

Code: Select all

display_library: win32, options="windebug"

Is there a new way to enable the enhanced debugger?

It looks like SMP is not configured in the Windows binary either. Are these still beta features since they don't compile them in by default?

Thanks,
-Ian

[stlw]

Is the "Bochs Enhanced Debugger" no longer included with the official distribution? I am using 2.3.7 since the config line below still works.

Code: Select all

display_library: win32, options="windebug"

Is there a new way to enable the enhanced debugger?

There is the only way - to start reading docs and/or configuration examples included in the release.

It looks like SMP is not configured in the Windows binary either. Are these still beta features since they don't compile them in by default?

SMP enabled binary runs more than 2x slower than single CPU. It could be included as another separate binary probably - but already not in this release.

[IanSeyler]

There is the only way - to start reading docs and/or configuration examples included in the release.

I tried that route as well. "display_library: win32, options="gui_debug" # use Win32 debugger gui" is listed in the sample config but gives an error "Unknown win32 option 'gui_debug'" when run with bochs.exe

Running bochsdbg.exe with the same config gives a different error "Config interface 'win32config' is required for gui debugger"

So not much help there...

Running bochsdbg without my config and specifying "gui_debug" does work.. must be an issue in the .bxrc file.

Thanks.

[jal]

There is the only way - to start reading docs and/or configuration examples included in the release.

No need to be rude. There's nowhere I can see a clear explanation of where it is gone.

Note, if you are looking for a graphical front-end for the bochs debugger, you may want to check out BFE. This is a package written by a Bochs user which can interface with the text based Bochs debugger. No linking is necessary. It's not part of Bochs, but you may find it useful.

...and that's it, as far as I can see. Back to 2.3.7 it is...


JAL

[IanSeyler]

No need to be rude.

My thoughts exactly..

Back to 2.3.7 it is...

It looks like it was an issue with my bochs config file. Running bochdbg with the "gui_debug" option does work correctly for me now. I rebuilt the config from scratch and all is good.

-Ian

[jal]

It looks like it was an issue with my bochs config file. Running bochdbg with the "gui_debug" option does work correctly for me now. I rebuilt the config from scratch and all is good.

Ok, sound like something I need to retry. Did you do it by hand, using a sample config file? Anyway, the Bochs man pages seem not up to date concerning the debugger.


JAL

[stlw]

It looks like it was an issue with my bochs config file. Running bochdbg with the "gui_debug" option does work correctly for me now. I rebuilt the config from scratch and all is good.

Ok, sound like something I need to retry. Did you do it by hand, using a sample config file? Anyway, the Bochs man pages seem not up to date concerning the debugger.


JAL

JAL, have no idea where you take Bochs man pages ... even on Bochs website (not the most up-to-date ones) help tells:

Some display libraries now support specific option to control their behaviour. See the examples below for currently supported options.
display_library: rfb, options="timeout=60" # time to wait for client
display_library: sdl, options="fullscreen" # startup in fullscreen mode
display_library: win32, options="legacyF12" # use F12 to toggle mouse
display_library: win32, options="gui_debug" # use win32 debugger gui frontend
display_library: x, options="hideIPS" # disable IPS output in status bar
display_library: x, options="gui_debug" # use GTK debugger gui frontend

Stanislav

[Combuster]

Try this:
man bochsrc

(assuming you have v2.4+ installed)

[jal]

JAL, have no idea where you take Bochs man pages ... even on Bochs website (not the most up-to-date ones) help tells:

I meant the help pages on the website, yes. I missed the "gui_debug" there, I looked at the debug section, as I quoted above. In 3.7 it was "guidebug", without the underscore, hence the confusion. I'll go read proper documentation now...


JAL

[stlw]

JAL, have no idea where you take Bochs man pages ... even on Bochs website (not the most up-to-date ones) help tells:

I meant the help pages on the website, yes. I missed the "gui_debug" there, I looked at the debug section, as I quoted above. In 3.7 it was "guidebug", without the underscore, hence the confusion. I'll go read proper documentation now...

JAL

JAL, there was no integrated GUI debugger in 2.3.7 ...
2.4 got the number mostly because of the GUI debugger capability, otherwise it would be called 2.3.8

Stanislav