Extending DOSBox debugger

Developer's Forum, for discussion of bugs, code, and other developmental aspects of DOSBox.

Extending DOSBox debugger

Postby DrMefistO » 2017-6-17 @ 22:17

I have few questions:
1) Where I can found amount of available memory during this running session? I mean count in bytes;
2) Launched executable segments information: I need to know segments information for the launched executable (code segment range, data segment range, etc., names);

The main goal of my efforts will be good IDA Pro debugger plugin for MS-DOS, without stupid bugs, and also extended DOSBox debugger itself.
DrMefistO
Newbie
 
Posts: 5
Joined: 2014-8-26 @ 13:42

Re: Extending DOSBox debugger

Postby ripsaw8080 » 2017-6-17 @ 22:50

1) If you mean free conventional memory, that can be determined from free memory blocks: try the debugger's DOS MCBS command.

2) You seem to want features of a source-level (symbolic) debugger; but the DOSBox debugger is system-level.
User avatar
ripsaw8080
DOSBox Author
 
Posts: 4011
Joined: 2006-4-25 @ 23:24

Re: Extending DOSBox debugger

Postby DrMefistO » 2017-6-17 @ 22:59

1) I mean some structure in DOSBox source code from which is possible to get this info.
2) Info from DOSBox source code.
DrMefistO
Newbie
 
Posts: 5
Joined: 2014-8-26 @ 13:42

Re: Extending DOSBox debugger

Postby ripsaw8080 » 2017-6-18 @ 00:16

I guess look in dos_memory.cpp and dos_execute.cpp; but I'm not sure what you're looking for. Again, don't expect to find any source-level info about programs running within the emulation.
User avatar
ripsaw8080
DOSBox Author
 
Posts: 4011
Joined: 2006-4-25 @ 23:24

Re: Extending DOSBox debugger

Postby DrMefistO » 2017-6-19 @ 11:26

For example, I want to know in which address my program will be loaded? Where I can find the load address of the launched executable?

The main purpose of my project, as I mentioned before, is to create debugger plugin for the IDA Pro. I will embed debugger server into DOSBox, and it will response with memory info, segments info, registers info, doing steps, etc.

http://www.osdata.com/system/physical/memmap.htm#MSDOS regarding thing memory table: is it possible to know size of the 0x600 region?
DrMefistO
Newbie
 
Posts: 5
Joined: 2014-8-26 @ 13:42

Re: Extending DOSBox debugger

Postby Mok » 2017-6-19 @ 14:57

Isn't there something similar already (I have never tried it though)? https://github.com/wjp/idados
User avatar
Mok
Newbie
 
Posts: 60
Joined: 2003-1-11 @ 11:59

Re: Extending DOSBox debugger

Postby DrMefistO » 2017-6-19 @ 16:35

Mok wrote:Isn't there something similar already (I have never tried it though)? https://github.com/wjp/idados

I know this project, but this is exactly what I'm thinking about it: "stupid bugs".
DrMefistO
Newbie
 
Posts: 5
Joined: 2014-8-26 @ 13:42


Return to DOSBox Development

Who is online

Users browsing this forum: No registered users and 3 guests