[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Debugging the map bug
From: |
Ground Zero |
Subject: |
Re: Debugging the map bug |
Date: |
Thu, 22 Jan 2004 18:22:26 +0200 |
On Thu, 22 Jan 2004 13:20:53 +0100 "Yoshinori K. Okuji" <address@hidden>
wrote:
> On Wednesday 21 January 2004 10:48, Ground Zero wrote:
> > I understand this bug is difficult to fix because it can't be easily
> > reproduced. Well, I've got it and I'm willing to debug it. Please
> > tell me what to do and what info you need from me and I'll help.
>
> Are you capable of assembly programming? Basically, you need to
> investigate what BIOS calls are used and how they are used. This
> requires that you replace BIOS calls with your own ones which show
> information about arguments and return values. If you are lucky, you
> might be able to create a virtual environment using Bochs, then you
> won't have to do so much assembly hacking, since you can use GDB in
> some degree.
>
> Probably the cause is that some BIOS calls are not "hooked" correctly.
> Your task would be to find out what is wrong and/or what is missing.
I'm actually a far cry off assembly programming. GDB would probably work, if
you mean watching for certain output and relaying it back to you. I can
probably serve as a somewhat more intelligent monkey that tries things and
reports how they came out. :)
Is it possible to still achieve something under these circumstances? Like for
example having the Grub developers prepare code that I can run and report what
happened?
--
GZ