Activity for slajerek
-
slajerek modified ticket #64
Missing debug symbols and breakpoints from kick ass .dbg file
-
I've checked this, it is working correctly in Retro Debugger, but you need to select segment "Patch" to have breakpoints. I remember I fixed similar problem in the past. Note, the latest version of Retro Debugger has indeed some bug as old segments seem to not be cleared, I'm investigating that.
-
Note, both are the same variable so in your case you can probably remove one of them. Not sure why this does not compile now, I'll check sometime soon. I think that I fixed similar problem with newest C++17 in RetroDebugger.
-
This may be related to gcc version and new requirements or includes. Which gcc version you are using? This compiled for me. Please note the development moved now to Retro Debugger, there was indeed a lot of mess related to the "#define byte unsigned char" as it clashes with emulators' own implementations. That was completely refactored in Retro Debugger (i.e. there's no more 'byte' definition and it was replaced to 'u8'). Please use older C++ flavour to compile this older C64 Debugger.
-
Interesting issue, thanks, will investigate.
-
Thanks, I'll investigate this. Note, I refactored the symbols in Retro Debugger already and development moved there.
-
Thanks. I added some small fixes around this in Retro Debugger as far as I remember in some rare cases when player used not usual tempered scale.
-
Blanc Screen in MacOS Big Sur 11.0.1
-
This may be related to gcc version. Which gcc version you are using? This compiles for me.
-
App window blank on MacOS Big Sur 11.0 Beta (20A5354i)
-
This is interesting. It seems it is related to problems with my old Debian build machine...
-
This is interesting. It seems it is related to my old Debian build machine...
-
PRG load doesn't work off command line
-
Thanks Zoltan, that's a bug, the Docs folder was added to hold documentation but something was messed up, I will update this.
-
Thanks for reporting. That has been fixed.
-
Shortcut for exit debugger
-
There's a shortcut already you can set for quit in Shortcuts settings, I've checked that it should be also available for Linux. Please confirm if it works for you and re-open if not.
-
This is already available on macOS, I need to add similar feature to Windows. If you have a C++ WinApi code available I'd love to paste it as simple storing position is not enough as this code needs to check also if resolution changed or external monitor is actually still there.
-
This works as intended, your PRG does not do proper init of IO and Kernal boot was not able to finish it before PRG was started. Anyway, a workaround for this is planned to allow user to select a snapshot which should be loaded on PRG start.
-
This works as intended, your PRG does not do proper init of IO and Kernal boot was not able to finish it before PRG was started. Anyway, a workaround for this is planned to allow user to select snapshot which should be loaded on PRG load.
-
This works as intended, your PRG does not do proper init of IO and Kernal boot is not able to finish it before PRG was started. Anyway, a workaround for this is planned to allow user to select snapshot which should be loaded on PRG load.
-
-
Crashing of system dialogs on Linux was fixed in 0.64.58, could you please confrm if it still crashes in the most recent version? By the way, selecting system directory as contents of Drive8 disk is not supported yet, so you need to select the d64 file to mount it.
-
Crashing of system dialogs on Linux was fixed in 0.64.58, could you please confrm if it still crashes in the most recent version? By the way, selecting system directory as contents of Drive8 disk is not supported yet.
-
Crashing of system dialogs on Linux was fixed in 0.64.58, could you please confrm if it still crashes in the most recent version?
-
Missing Debugger Plugin files
-
fixed in 0.64.58
-
It is just creating a new file, good point about > vs >>
-
1) This is in progress. 2) Actually I discussed similar functionality heavily with Digger at X2018 :) I have some ideas how to do that. 3 and 4) This is in progress, an experimental SDL2 ImGui version will be released soon.
-
Crash in file open dialog
-
This has been fixed in latest version 0.64.56.8. Please confirm and reopen if this is still an issue.
-
The Ctrl+F5 view has been optimised, please check in the next upcoming version (0.64.56.8b) Also you may speed emulation up by changing SID engine to FastSID.
-
Nice idea! I will add to the TODO list.
-
Thanks, that's bug indeed. These are my test plugins which are not for public release. The Spiral actually is an effect from Samar's NGC 1277 demo, I am thinking to release this as example how to make plugins someday. I will remove these includes.
-
Thanks, that's bug indeed. These are my test plugins which are not for public release. The Spiral actually is a effect from Samar's NGC 1277 demo, I am thinking to release this as example how to make plugins someday. I will remove these includes.
-
Changes to compile on macOS 64bit + upped sources to 2.75. Updated readme to 2.75
-
Changes to compile on macOS 64bit + upped sources to 2.75
-
Changes to allow macOS 64bit compilation. Upped sources to 2.75
-
1) Actually this works almost as you wrote: D 1000 2000 file.txt Other points are interesting. I plan to add support to Vice monitor anyway that might fix this for you.
-
Yes, this seems to be related to the fact that Kernal is initialising. You can wait a bit for the Kernal to finish initialise by adding -wait <ms> parameter, also I suggest to apply a "Fast kernal patch" in Settings, so the init is quick. Normally around 500ms should be enough to get the Kernal going.</ms> Please confirm if adding -wait parameter fixed your problem. I have a plan to rewrite this and add a quick init based on snapshots, anyway this is still WIP.
-
Yes, this is related to the fact that Kernal is initialising. You can wait a bit for the Kernal to finish initialise by adding -wait <ms> parameter, also I suggest to apply a "Fast kernal patch" in Settings, so the init is quick. Normally around 500ms should be enough to get the Kernal going.</ms> I have a plan to rewrite this and add a quick init based on snapshots, anyway this is still WIP.
-
Yes, this is an odd error in the GTK when custom event loop is created and this also varies between GTK versions. To overcome this temporarily you can select "Use system dialogs ON/OFF" in the settings menu which is a workaround for this error.
-
can a disassembly be dumped to a file?
-
Yes, you can disassemble code in Monitor (ctrl+f8) and then send output to a file (please check HELP in the Monitor)
-
This is partially possible using profiler and export to profile file, however a kind of stack trace would be cool to have indeed.
-
This was changed for potential new users of JOE, so that we can have a single conventional exit Although I understand you prefer to have new users, I do not understand why you decided to not support old users that were using this tool for more than 20 years. I have just again saved file instead of cancelling it... that's it and made me really angry. I am sure new users prefer easier editors. Thanks for these 20 years of JOE, it's high time for me to switch to editor in which I am not confused all...
-
double quote key not working in C64 screen nor monitor
-
Actually you do not need to put filename in quotes. But the quotes do not work indeed.
-
Yes, but I plan to integrate real gamepads someday.
-
Display 1541 registers after "DEVICE 8" command in monitor mode
-
Interesting, actually I had to install these libraries on my Debian (both x64 and i386): sudo apt-get install libxcb-util-dev sudo apt-get install libxcb-util0 sudo apt-get install libxcb-util0-dev And that was enough to start it. Maybe these packages are broken and not linked correctly in Ubuntu? You can always put the libxcb-util.so.0 manually in somewhere and add its path to LD_LIBRARY_PATH and then reload with ldconfig. Are you sure you have them installed? :-) These libraries are needed for...
-
Interesting, actually I had to install these libraries on my Debian (both x64 and i386): sudo apt-get install libxcb-util-dev sudo apt-get install libxcb-util0 sudo apt-get install libxcb-util0-dev And that was enough to start it. Maybe these packages are broken and not linked correctly in Ubuntu? You can always put the libxcb-util.so.0 manually in somewhere and add its path to LD_LIBRARY_PATH and then reload with ldconfig. These libraries are needed for copy-paste and are needed by the libclipboard...
-
Interesting, actually I had to install these libraries on my Debian (both x64 and i386): sudo apt-get install libxcb-util-dev sudo apt-get install libxcb-util0 sudo apt-get install libxcb-util0-dev And that was enough to start it. Maybe these packages are broken and not linked correctly in Ubuntu? You can always put the libxcb-util.so.0 manually in somewhere and add its path to LD_LIBRARY_PATH and then reload with ldconfig. These libraries are needed for copy-paste and are needed by the libclipboard...
-
I think I fixed this by automatically clearing markers on PRG load, will be in next version. Please confirm.
-
Display 1541 registers after "DEVICE 8" command in monitor mode
-
Display 1541 registers in monitor mode after DEVICE 8
-
Thanks for the bug report, this needs to be changed. This will be fixed in next version, please confirm after Release. Duplicate of #25
-
This will be fixed in next version, please confirm after Release.
-
Thanks for reporting. Will be updated in next version, please confirm after Release.
-
I think I fixed this, will be in next version. Please confirm.
-
Unable to show the state of chips on macOS
-
You can change the keyboard shorcut in debugger in Settings menu, but also disable default macOS keyshortcut too. Works for me as I disabled all default OS keyboard shortcuts in macOS.
-
Notification for going with Tabs
-
Now it is possible to select border width,
-
Thanks for the bug report, this needs to be changed.
-
Are you talking about controlling C64 via joystick port? It is possible to switch the joystick on via Ctrl+Y key and then use keyboard arrows. OS joysticks (analog/digital) are not supported yet.
-
Ctrl+K Q (quit) behaviour is wrong
-
edit cpu registers in CPU status bar
-
jukebox
-
Win32 + bug fixes
-
vs2008-config
-
edit cpu registers in CPU status bar: CViewBaseStateCPU, CViewC64StateCPU, CViewDriveStateCPU
-
win32 project, code cleanup
-
v0.63.1: win32 assembly bug fix; drive trap (experimental); basic compatible auto-run
-
bug fix: c64 cpu set x was setting a
-
JukeBoxDemo.c64jukebox
-
jukebox
-
readme fix
-
switch sound on/off, updates to jukebox json var names, tweaks
-
v0.62
-
The copy paste is planned however I'm not sure yet how to make it usable with good UX... by the way you can PASTE to memory dump (hex values). This is already possible just press alt+shift in memory dump view (where hex values are visible).
-
The copy paste is planned however I'm not sure yet how to make it usable with good UX... This is already possible just press alt+shift in memory dump view (where hex values are visible).
-
I confirm this 2017/07/04 is still broken on my pi from apt-get. matchbox-keyboard 0.1 Copyright (C) 2007 OpenedHand Ltd.
-
I confirm this 2017/07/04 is still broken.
-
VICE is emulator of various Commodore devices, intended to work quickly and be optimised for different platforms (like AmigaOS). C64 Debugger adds huge overhead to the emulation engine. It is doable but definitely not simple and could make ports to low-end platforms suffer.
-
CPU flags aren't displayed corretcly in "step" mode...
-
This is fixed with v0.60 release and Vice 3.1 upgrade. Thanks again for reporting!
-
This will be fixed with v0.60 release. Thanks again for reporting!
-
Cartridge is sometimes not initialised properly after machine reset
-
Fixed with Vice 3.1 integration
-
Fixed in 0.57
-
Loading NTSC snapshot into PAL machine crashes debugger
-
PC breakpoint sometimes does not stop code execution
-
Fixed with Vice 3.1 integration.
-
Can't load using VICE auto-load mechanism
-
Can't load using VICE auto-load mechanism
-
C64 debugger can't load using VICE auto-load mechanism
-
Cartridge is sometimes not initialised properly after machine reset
-
When snapshot is loaded then selected settings are not updated in the Settings
1 >