OSDev.org

The final release of Bochs 2.5 is out now.
The sources and binary package for Linux and Windows are available for download.
Win32 package with internal debugger enabled and Win64 binaries package will be uploaded soon.

Brief summary of changes:

Bochs repository moved to the SVN version control !

! Fully configurable CPU to emulate with a single .bochsrc option !
- 10% (ST) to 50% (SMP) CPU emulation speedup !
- Implemented support for new x86 ISA extensions, Bochs is aligned with
latest published Intel Architecture Manual (rev 040, AVX rev 011):
- XSAVEOPT, AVX/AVX2/FMA/F16C, BMI1/BMI2, SMEP, INVPCID, TSC-Deadline
- VMX: VMX Preemption Timer, Pause Loop Exiting and VM Functions
- Implemented support for AMD SSE4A/XOP/FMA4/TBM instruction sets
- Networking: introduced new networking module 'slirp'
- Harddrive: fixed buffer overflow causing Bochs crash in LBA48 mode
- VGA: Added PCI ROM support to cirrus and pcivga and moved ROM loading
for the ISA case to the vga code (SeaBIOS now usable by Bochs)
- Sound: ported ES1370 soundcard emulation from Qemu
- Continuing configure rework, check for more removed configure and .bochsrc
options and their replacements !
- LGPL'd VGABIOS updated to version 0.7a

Stanislav

Bug Report - Compile error when instrumentation is enabled [link=https://sourceforge.net/tracker/?func=detail&aid=3443865&group_id=12580&atid=112580]SF Bug entry[/url]

cpu/tasking.cc:482 should be

Oh, it's not dead, this fact is great. Bochs helped me very much while hunting for bugs in palacios.

Quick question, I downloaded the linux source version and configured it to enable the internal debugger and was successfully able to get it to compile on my cygwin box in win7. I am able to get a test kernel running in bochs but for the life of me cant figure out how to get the internal debugger to show up. There used to be a seperate program called bochsdbg.exe when you used it for the debugger but cant seem to find it in my bochs directory, though I have the other bximage/bxcommit tools to generate images. I have set the "--enable-x86-debugger/--enable-disasm" options in the configure script as well as set "display_library: win32, options="gui_debug" in the bochrc.txt file to use it.

If I try to run the bochs program from the command prompt all I get is the normal startup and not the debugger, is there a special command to run it that Im overlooking or cant find. Ive spent quite a bit of time searching google for a answer and reading through the bochs docs but cant seem to get it to show up, maybe im not using the correct search words in google. I did notice that when I look through the bochsout.txt file when it closes that it doesnt mention it being configured for debugging mode but I know I set the options, could it be a borked compile/install, maybe I need to compile it with vc++ ?

Thanks in advance, going crazy trying to figure out how to get it run.

--EDIT: just downloaded the windows .exe, ran the setup and the newest version has bochsdbg.exe. My fault as I was using the win64 one which just runs bochs, but still wondering why when I compile it from source with the configure options it doesnt show up with the other programs,I have successfully cross-compiled programs before on both win/linux as well as setup a cross-compiler for my own os on cygwin so I know how to use a cmd, must of missed something simple.

beyondsociety wrote:Quick question, I downloaded the linux source version and configured it to enable the internal debugger and was successfully able to get it to compile on my cygwin box in win7. I am able to get a test kernel running in bochs but for the life of me cant figure out how to get the internal debugger to show up. There used to be a seperate program called bochsdbg.exe when you used it for the debugger but cant seem to find it in my bochs directory, though I have the other bximage/bxcommit tools to generate images. I have set the "--enable-x86-debugger/--enable-disasm" options in the configure script as well as set "display_library: win32, options="gui_debug" in the bochrc.txt file to use it.

If I try to run the bochs program from the command prompt all I get is the normal startup and not the debugger, is there a special command to run it that Im overlooking or cant find. Ive spent quite a bit of time searching google for a answer and reading through the bochs docs but cant seem to get it to show up, maybe im not using the correct search words in google. I did notice that when I look through the bochsout.txt file when it closes that it doesnt mention it being configured for debugging mode but I know I set the options, could it be a borked compile/install, maybe I need to compile it with vc++ ?

Thanks in advance, going crazy trying to figure out how to get it run.

--EDIT: just downloaded the windows .exe, ran the setup and the newest version has bochsdbg.exe. My fault as I was using the win64 one which just runs bochs, but still wondering why when I compile it from source with the configure options it doesnt show up with the other programs,I have successfully cross-compiled programs before on both win/linux as well as setup a cross-compiler for my own os on cygwin so I know how to use a cmd, must of missed something simple.

You compiled it with wrong option.

--enable-x86-debugger enables x86 HW debugging functionality as DR0-Dr7 debug registers and HW breakpoints emulation
--enable-debugger, --enable-debugger-gui you didn't enable.

Reading docs always could help in such a cases.
Bochs user docs:

8.11. Using Bochs internal debugger
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.

You can now conditionally compile in a GDB like command line debugger, that allows you to set breakpoints, step through instructions, and other useful functions. If there isn't a command for something you believe is generally useful for the debugger, let me know and I'll implement it if possible.

To use the debugger, you must configure Bochs with the --enable-debugger and --enable-disasm flags. For example:

./configure --enable-debugger --enable-disasm

Stanislav

Tks stlw. I read through that part and somehow missed it originally and must of thought it said "x86-debugger", will give it a go when I get home.