Page 2 of 2
Re: XROAR and Windows 10
Posted: Thu Feb 11, 2016 12:44 pm
by pser1
Hello Ciaran,
I have been using the last snapshot and worked great ...
But it failed when I wanted to debug a program using the GDB
The message says something like:
; --------------------------------------------------------------------------------------------------------
Files that give a description of the problem:
C:\Users\serrat\AppData\Local\Temp\WERD5F8.tmp.WERInternalMetadata.xml
C:\Users\serrat\AppData\Local\Temp\WERECE3.tmp.appcompat.txt
C:\Users\serrat\AppData\Local\Temp\WERED8F.tmp.hdmp
; --------------------------------------------------------------------------------------------------------
I am attaching them 'zipped' here, maybe this could help.
You can count on me to do any needed test
cheers
pere
Ps Of course, version "v0.33.1-2015-33312 w64" works flawlessly
Re: XROAR and Windows 10
Posted: Wed Feb 24, 2016 8:39 am
by sixxie
Now that I've fixed my Wine fonts issue (none appearing, even with fonts-wine package installed - fix was to use winetricks), I can look into this - first quick test showed gdb working though - both w32 and w64. Is there anything you do other than starting with -gdb and then connecting to it to trigger this?
Re: XROAR and Windows 10
Posted: Wed Feb 24, 2016 8:52 am
by pser1
Hello Ciaran,
this is the bat file I use to start both GDB and XRoar:
Code: Select all
cd..
copy ..\XRoar\DOS-ROMs\dplus50.rom ddos40.rom
copy ..\XRoar\ROMs\d64rom1V31.rom d64_1.rom
copy ..\XRoar\ROMs\d64rom2V31.rom d64_2.rom
start xroar -gdb -machine dragon64 -machine-cpu 6309 -extbas d64_1.rom -altbas d64_2.rom -machine-cart dragondos -cart-rom ddos40.rom -force-crc-match -disk-write-back -joy-left 0,0:1:0 -kbd-translate -lp-file ..\XRoar\sortida.txt
pause "press any key when XRoar is running"
m6809-gdb -ex "layout asm" -ex "layout regs" --eval-command="target remote localhost:65520"
del *.rom
This bat works flawlessly with the old XRoar "v0.33.1-2015-33312 w64"
cheers
pere
Re: XROAR and Windows 10
Posted: Sun Feb 28, 2016 6:22 pm
by pser1
Hello Sixxie,
I am uploading here a zip file that contains the environment where I test this last version.
Just execute the .BAT file
I have put inside a folder two screenshots, one before executing a program (1 byte) in XRoar
and the other with the crash
In the Windows event viewer I have found just this small file with info about the problem.
If your exe does save info into another folder, just tell me and I will upload it here too
cheers
pere
Re: XROAR and Windows 10
Posted: Tue Mar 01, 2016 7:46 am
by sixxie
Unfortunately all of that works fine under Wine - not crashing for me!
Do you have the .hdmp (mdmp?) file from running this version? winedbg seemed to be able to do something with those, and it might give me a clue where the crash is happening.
Re: XROAR and Windows 10
Posted: Tue Mar 01, 2016 10:29 am
by pser1
Hello,
I have found these two files inside a folder.
I have zipped the whole folder and attached it here
Hopefully this will help find the problem
cheers
pere
Re: XROAR and Windows 10
Posted: Wed Mar 23, 2016 4:02 pm
by pser1
Hi Ciaran,
I have seen on "
http://www.6809.org.uk/tmp/xroar/"
a new snapshot of XRoar (2016-15132) from yesterday ...
I have downloaded it and it works without GDB, but as soon as it is
intercepted by GDB crashes as did last snapshot ...
I assume I wil have to wait untill you tell me it works again with GDB.
If you need me to do any test, just let me know. Thanks.
cheers
pere
Re: XROAR and Windows 10
Posted: Wed Mar 23, 2016 5:45 pm
by sixxie
Yeah sorry, that was just a snapshot that killed off Control+C in the SDL interface for someone else (long since undocumented, doesn't work in the GTK+ interface).
I've not made any progress on the gdb weirdness - wine doesn't give me anything useful with your last set of mdmp/hdmp files I'm afraid.
Re: XROAR and Windows 10
Posted: Tue Oct 04, 2016 12:02 pm
by Gareth_O'Flaherty
The latest iteration of Windows and XRoar now working perfectly with one another! Happy days.
Re: XROAR and Windows 10
Posted: Tue Oct 04, 2016 4:34 pm
by sixxie
Sounds like the move to SDL2 is a big win for Windows then.
Shame about its keyboard handling: extra platform-dependent code is required to handle special characters like Ñ on the Dragon 200-E in translated mode. SDL1 made that pretty straightforward.