Debugger interface

[Dr. MefistO]

Hi!

I'm writing IDA debugger plugin for WinUAE, and it requires some info about debugger functions of this emulator. Where I can find such functions?:

1. Read memory from some address;
2. Write memory to some address;
   
3. Get register value;
4. Set register value;
   
5. Set breakpoint at some address (read/write, execution);
6. Clear breakpoint at some address;
   
7. Attach to some program;
8. Pause execution of program;
9. Stop execution of program;
   
10. Continue execution;
11. Execute one instruction;

I mean functions somewhere in debug.h, or debug_win32.h.

[Toni Wilen]

They don't exist. They are all in debug.cpp, there was never need to call them from outside of debugger.

\.\pipe\WinUAE named pipe may be also useful, it can be used to send and receive debugger, input event, etc commands.

[Dr. MefistO]

Toni Wilen, ok, I can make them outside (for my version).
But, anyway, could you point me to that functions?

I don't understand that system with chars, that should be sent to console to execute commands.

For example:

static void step(BOOL over)
{
	if (over)
		_tcscpy(internalcmd, _T("z"));
	else
		_tcscpy(internalcmd, _T("t"));
	useinternalcmd = TRUE;
	inputfinished = 1;
}

Or tell me about pipe commands. Are there some commands for my list?

[Toni Wilen]

Sources come with ipctester.cpp that was used to test pipe sending and receiving. Perhaps it helps.

It is nearly same as writing debugger commands directly to console window, only difference is that it supports also other than debugger commands which requires prefixes or targeting command. (Check uaeipc.cpp for prefixes)

All debugger routines expect command as a string, then they parse it and do the command. There is no routines that take "normal" parameters. (like address and length). As I said, there as never need previously

For example "instruction_breakpoint()" takes string, then parses it, then adds/removes breakpoint.

There is also plans for "real" UAE debugger interface: https://github.com/FrodeSolheim/fs-uae/issues/63

[Dr. MefistO]

Thank you! I think, now I will do that!)

[Dr. MefistO]

Is there any posibility to start new process in WinUAE from that pipe? Or by any other way.

For example, I have already copied binary in some directory of WinUAE, and I just want start it. First, I don't know how to start, and then I need know start IP.

Which functions are responsible for starting binaries in WinUAE?

[Toni Wilen]

What do you mean by "process"? Amiga process?

[Dr. MefistO]

I mean process or task which will be created when I'll execute my amiga-hunk binary in WinUAE.

[Toni Wilen]

Originally Posted by Dr. MefistO

I mean process or task which will be created when I'll execute my amiga-hunk binary in WinUAE.

There is no support in UAE for running Amiga executables. It does not need to run any programs. Some sort of remote CLI may be something you want.

But why not just create startup-sequence that runs program(s) you need?

[Dr. MefistO]

Because I want connect to my executable at its startup and debug it by pipe interface.

[Toni Wilen]

There is nothing like that and this is too high level for my tastes, sorry.

Existing debugger features don't know nothing about Amiga processes or tasks. It is mainly done for hardware level debugging programs that take over the system.

(Most of these probably can be done by simple AmigaDOS loader program, if someone bothers..)

[Dr. MefistO]

Originally Posted by Toni Wilen

Existing debugger features don't know nothing about Amiga processes or tasks. It is mainly done for hardware level debugging programs that take over the system.

But there is T command for debugger which dumps current process/task list.

How do you think, such variant will be good?:
1) Patch amiga-executable at start with infinite loop (store original bytes too);
2) Ask user for starting executable with needed params (program will hang at start and will become a current task);
3) Connect to WinUAE by Pipe;
4) Restore original bytes at entry point and do needed work with this process.

[Toni Wilen]

It is only dumps data, it does not do anything with it.

I'd put write to absolute address (that does not point to anything important, like $100 or $ffffffff or whatever) at the beginning of program, when program starts it triggers break point you have set before loading the program. No need to care about processes or tasks or anything else.

[Dr. MefistO]

So, I should put opcode of writing value to some independent address and set breakpoint to it, right? Hmm, good idea..)

But what difference with infinite loop?

Problem is that I have no source code for this program. So, it will be a patch.

P.S. In your way it will popup debugger's window then? It is bad.