Discussion:
debugging
(too old to reply)
c***@CSIC.UMD.EDU
2005-02-16 23:01:40 UTC
Permalink
Any suggestions with
regards to debugging
project2?
Iulian Neamtiu
2005-02-17 17:46:01 UTC
Permalink
Most of the time you'll get an Exception 12 or 13. Take the value of the
EIP (program counter at crash site). If it crashes in the kernel (the
selectors and EIP will tell you that), then

$ cd buils
$ ../scripts/eipToFunction geekos/kernel.syms <eip value>
or
$ objdump -d geekos/kernel.exe | less
and look up the offending address using '/' to search it.

If it's an userland crash:
$ objdump -d user/<program>.exe | less
and look up the offending address.

Iulian
Post by c***@CSIC.UMD.EDU
Any suggestions with
regards to debugging
project2?
Timothy Finley
2005-02-19 04:10:23 UTC
Permalink
Post by c***@CSIC.UMD.EDU
Any suggestions with
regards to debugging
project2?
I'd also highly suggest looking at the bochs.out log file (as well as the
other debugging options you can turn on in bochs). The log gives more
information than the exception register dump you get on screen. Some
things in there helped me fix a problem I've had for 2 days (the log file
won't help a lot but it can give you another place to look if you are
really stuck).

Tim

Continue reading on narkive:
Loading...