On Thu, Nov 09, 2006 at 12:57:29AM +0100, Marcel Kilgus wrote:
> Daniel Jacobowitz wrote:
> >> Leaving that aside, if I do set the breakpoint correctly at virtual
> >> address (e.g.) 0xC0123456 qemu will (correctly I guess) cause an
> >> exception for code offset 0x123456 (as CS base is 0xC000)
Hi All,
My name is Takanori Kasai, work for Fujitsu.
This is a first time to send mail.
I am doing the development of Xen.
Then, I found the key that was not able to be input with Japanese keyboard(106).
I think that it is a cause by lack of some keys
in Japanese keymap and the key symbol table
Daniel Jacobowitz wrote:
>> Leaving that aside, if I do set the breakpoint correctly at virtual
>> address (e.g.) 0xC0123456 qemu will (correctly I guess) cause an
>> exception for code offset 0x123456 (as CS base is 0xC000). GDB
>> however then doesn't recognize its own breakpoint as it only r
On Thu, Nov 09, 2006 at 12:33:05AM +0100, Marcel Kilgus wrote:
> Leaving that aside, if I do set the breakpoint correctly at virtual
> address (e.g.) 0xC0123456 qemu will (correctly I guess) cause an
> exception for code offset 0x123456 (as CS base is 0xC000). GDB
> however then doesn't recogni
Fabrice Bellard wrote:
> The breakpoints are set for a given virtual address. So IMHO testing
> only the EIP value instead of EIP + CS.base is not logical...
That I just check for EIP is a convenience for me. The code is linked
to 0x0010 but moves itself to the virtual address 0xC010 (CS
s
Marcel Kilgus wrote:
/me wrote:
Having to always set them both in the high and low area is a bit
cumbersome to say the least. Any suggestion on what I'm missing or can
do to get breakpoints working properly again?
Okay, the QEMU source code was a lot more readable than I expected it
to be, s
/me wrote:
> Having to always set them both in the high and low area is a bit
> cumbersome to say the least. Any suggestion on what I'm missing or can
> do to get breakpoints working properly again?
Okay, the QEMU source code was a lot more readable than I expected it
to be, so I had a look myself
Hetz Ben Hamo wrote:
> Perhaps you could submit your printf's so other people can learn from
> them please?
Well, most of them I no longer have; they slowed things down, so I
deleted them once I had the problems fixed. Besides, they were probably
too idiosyncratic to help other people much.
Ho
On Wed, 2006-11-08 at 14:31 +0100, wangji wrote:
francis,
why not leave your development_available as readonly_access (svn_like or=20
anyftp) it would be great for learning !
I probably will release it once I finish my thesis. However, at present, it's not in good shape to be built by oth
francis,
why not leave your development_available as readonly_access (svn_like or
anyftp) it would be great for learning !
(to complement wikipedia_microkernel !!! )
just to recall on linux_kernel stuff
1998 Bowman effort's reverse eng
concrete (as-built) architecture of the Linux kernel : (199
10 matches
Mail list logo
