RE: [Bochs-developers] Monitoring I/O ports traffic

[Christopher N. <paradox@BBHC.ORG>]

My suggestion is to --enable-gdb-stub and --enable-iodebug.  Compile
your kernel with debug symbols.

Then run bochs with gdb-stub debugging enabled.
Next, run ddd kernel &
Type target remote localhost:1234 into the ddd console.
Break <the function that's broken>
Cont

This will let you break into the debugger when the code you want to
debug is about to execute.  Step through it and watch the results from
the iodebug messages.  You might need to tail -f error.log, depending on
your setup.

-=3D{C}=3D-

> -----Original Message-----
> From: boc...@li... [mailto:bochs-
> dev...@li...] On Behalf Of magicfox
> Sent: Wednesday, January 25, 2006 7:41 AM
> To: Viktor Kleen
> Cc: boc...@li...
> Subject: Re: [Bochs-developers] Monitoring I/O ports traffic
>=20
> >> Use --enable-iodebug at the configure stage then setup .bochxrc
file
>=20
> > After playing a little bit with it, I've only got one problem: There
are
> > lots of messages from PIT screwing the log up, so I can't find the
> > things that are interesting.?
> > Do you also know a solution to this?
>=20
> CVS/bochs/docs-html/iodebug.html
> is a good start ;-)
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD
SPLUNK!
>
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=3D=
121642
> _______________________________________________
> bochs-developers mailing list
> boc...@li...
> https://lists.sourceforge.net/lists/listinfo/bochs-developers