| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* gdbstub: small cleanup and clarification
Old GDBs expected the regnum values for some registers to be hardcoded.
This is no longer the case with GDB clients that support target.xml.
We expect the GDB client to support target.xml (and won't support the
'g', 'G', 'p', and 'P' commands unless it is sent).
* gdbstub: add mips (tested with indy_4610)
* gdbstub: add m68k (tested with macii)
* gdbstub: add support for executing MAME debugger commands from the GDB client
It's now possible to send MAME debugger commands, such as "cheatinit",
"snap", etc...
Try not to use "bpset" and such commands, they may confuse the GDB
client. Also don't use commands such as "step" and "go", they will
definitely confuse the GDB client.
* gdbstub: fatalerror() when socket can't be opened
|
| |
|
|
| |
I'm assuming atronic.cpp was supposed to be Windows-1252 with Euro currency symbol encoding. Everyone please use UTF-8 for source files.
|
| |
|
|
| |
These unused parameters don't cause any warnings, so I suggest they shouldn't be commented; make the implementations match their declarations.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
z80 was tested with pacman and m6502 was tested with apple2e.
Side-effects must be disabled before reading memory, otherwise apple2e
starts failing after the first read to 0xc080.
Since GDB doesn't support those processors, I made up the features name
with "mame.<cpuname>". I also had to choose the registers to export in
the target.xml file, and since I don't have any experience with these
processors I don't know if I made the best choice.
|
|
|
* gdbstub: added new GDB stub debugger
This debugger can be used to connect to an external debugger that
communicates using the GDB Remote Serial Protocol, such as GDB itself
or many other GDB frontends.
Currently i386 (ct486), arm7 (gba), and ppc (pmac6100) are supported.
* gdbstub: enable GDB stub debugger in mac and windows builds
|