| |
C64 65XE NES Debugger V0.64.58.4 [2021] |
Website :
https://sourceforge.net/p/c64-debugger/
Credits :
Code | .... | Slajerek of Samar Productions |
Graphics | .... | Isildur of Samar Productions |
Idea | .... | Bacchus of Fairlight |
| | Brush of Elysium |
| | Digger of Elysium |
| | Dr.J of Delysid, Finnish Gold |
| | Isildur of Samar Productions |
| | Mr Wegi of Elysium |
| | Slajerek of Samar Productions |
| | Slammer of Camelot, Starion |
| | Stein Pedersen of Offence, Panoramic Designs, Prosonix |
Test | .... | Bacchus of Fairlight |
| | Brush of Elysium |
| | Digger of Elysium |
| | Don Kichote of Avatar, Caution, Reliance, Samar Productions |
| | Dr.J of Delysid, Finnish Gold |
| | Golara of Desire, Samar Productions |
| | Isildur of Samar Productions |
| | Scan of Desire, House Designs |
| | Slajerek of Samar Productions |
| | Slammer of Camelot, Starion |
| | Yugorin of Samar Productions |
Help | .... | Yugorin of Samar Productions |
Download :
Look for downloads on external sites:
Pokefinder.org
User Comment Submitted by Slajerek on 12 May 2021
@mace what do you mean by "main thread"? there's only one CPU in the C64, so no threads :) of course it is possible to see the IRQ code, if you want to debug the IRQ the easiest way is just to set a breakpoint there. | User Comment Submitted by Mace on 13 April 2021
Am I correct to assume that it is impossible to see the IRQ code that is running? The assembler view at the right-hand side of the screen only shows the main thread. | User Comment Submitted by Burglar on 6 March 2021
@map, incredible! I applied all your patches and recompiled and holy cow, it works \o/
thanks a lot for the tips :) | User Comment Submitted by map on 6 March 2021
@Burglar: with the commit from 23.02.21 I had to perform following changes to build successfully on my Ubuntu20.10:
AtariWrapper.mm line 150:
//volatile UWORD CPU_regPC;
esc.c line 137:
extern int c64d_is_cpu_in_jam_state;
C64D_Version.h line 5-7:
#define RUN_COMMODORE64
//#define RUN_ATARI
//#define RUN_NES
Additionally I had some odd behaviour when trying to use an older version again.
This helped to fix it:
./c64debugger -clearsettings | User Comment Submitted by Burglar on 6 March 2021
Just tried this on a relatively clean Ubuntu 20.04 LTS, here are my findings:
1. error libxcb-util.so.0
Same error as reported by others. Installing libxcb stuff does not fix it.
2. compiled from source
executable now "works", except that the vice window is completely black. I see memory output, but nothing useful: pc at 0000, I can scroll through memory, but nothing seems to be initialized.
memory seems filled with the high-byte of the memory page. | User Comment Submitted by map on 26 February 2021 User Comment Submitted by Remdy on 26 February 2021
Thanks but maybe you should link it static? still get the ./c64debugger: error while loading shared libraries: libxcb-util.so.0: cannot open shared object file: No such file or directory | User Comment Submitted by Isildur on 24 February 2021
To max speedup C64DBG on latest Win10 build set:
Use only first CPU: NO (UI settings)
and (optional):
VIC display rec: Each rasterline (Emulation settings) | User Comment Submitted by HIGHLINE on 23 February 2021
This looks decently incredible.Happy BD man :) so after this you can continue awesoming your "Gray Tracker" pretty please :D !!! | User Comment Submitted by Digger on 22 February 2021
$ff years Marcin! Scene would not be what it is without this tool! <3 | User Comment Submitted by Carrion on 22 February 2021
Happy BDay Slajerek!
Thanks for your great work with the debugger! |
|
|
|
| Search CSDb |
| Navigate | |
|
| Detailed Info | |
|
| Fun Stuff | |
· Goofs · Hidden Parts · Trivia
|
|
| Forum | |
|
| Support CSDb | |
|
| |
|