Re: Some questions regarding bochs

On Fri, Jul 25, 2014 at 9:58 AM, ilan kozov <[email protected]> wrote:
> hey gene,
>
> Thanks for your answer!,  but i dont want to put brwakpoints after
> interuprs. I'm trying to automaticly trace all the opcodes executed and
> their addresses until OS boots up. So i need to this in single command
> specifieng the wanted addresses or somehow script boch, are you familiar
> with those?

I believe this would need to be multiple disassemble statements but at
least I've had excellent luck pasting in commands like this with my X
terminal emulator so never explored scripting.

> On 2014 7 25 04:24, "Gene Cumm" <[email protected]> wrote:
>>
>> On Thu, Jul 24, 2014 at 7:43 PM, ilan kozov <[email protected]> wrote:
>>
>> I can't speak for the first two questions however I can speak from
>> experience with the third.
>>
>> > - When using trace option in the debugger, can i trace specific
>> > addresses?
>> > for example, when tracing MBR execution i don't want to trace BIOS code.
>>
>> Why not disassemble by range?
>>
>> disassemble 0x7c00 0x7dff
>>
>>
>> http://bochs.sourceforge.net/doc/docbook/user/internal-debugger.html#AEN4015
>>
>> Otherwise, you can skip the entire disassembly part and step through
>> things while setting break points after any interrupts and continuing
>> over break points.
>>
>> --
>> -Gene



-- 
-Gene

A: Because it messes up the order in which people normally read text,
especially the archives of mailing lists.
Q: Why is Top-posting such a bad thing?

"No one ever says, 'I can't read that ASCII(plain text) e-mail you sent me.'"

------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds