30 September 2019, 23:39 | #101 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
|
19 October 2019, 04:35 | #102 |
Registered User
Join Date: May 2015
Location: Kirkland, Washington, USA
Posts: 56
|
I finally got around to try this, and it is very impressive, thank you for doing all this work.
I ran into one issue - not sure if this is just me: using the sample workspace, I can place/remove breakpoints before launching, I can step over and into just fine. However once I hit the first breakpoint, I can’t place or remove any breakpoints - if I do, the emulation in fs-uae will hang. This is on Windows 10. |
19 October 2019, 17:56 | #103 | ||
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
Quote:
I'll try it later this weekend. |
||
19 October 2019, 19:40 | #104 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
I've added an issue to github: https://github.com/prb28/vscode-amig...mbly/issues/96 Thanks for reporting... now it's time for debugging |
|
20 October 2019, 04:11 | #105 |
Registered User
Join Date: May 2015
Location: Kirkland, Washington, USA
Posts: 56
|
Yay, it is not just a bug on my machine :-)
Now for me to figure out how I can configure my code to work with it |
20 October 2019, 18:51 | #106 |
OCS forever!
Join Date: Mar 2019
Location: Birmingham, UK
Posts: 418
|
I don't know if something has changed on 0.18 but my breakpoints are no longer working. If I download the example workspace and build/run within VSCode then it works ok. But if I compile outside of VSCode and then debug it stops on entry fine (and can single step). But any breakpoints I've set are ignored and if I hover over them in vscode it says "Debug information not resolved retrieved"
This is on Win10. Edit: Here's an example, just create a batch file in the root of your example gencop workspace and run it to compile. Then run the debug from vscode and see if it stops and and/or gives the debug not resolved message above. Code:
set ObjDir=Build set OutDir=fs-uae\hd0 set BuildParam=-m68000 -Fhunk -linedebug set LinkParam=-bamigahunk -Bstatic bin\vasmm68k_mot.exe %BuildParam% -o %ObjDir%\gencop.o gencop.s bin\vlink.exe %LinkParam% -o %OutDir%\gencop %ObjDir%\gencop.o Last edited by Antiriad_UK; 20 October 2019 at 19:23. |
20 October 2019, 20:51 | #107 | ||
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
Thanks for the bat, I'll try it as soon as I can add a new breakpoint with the extension ! Quote:
There is the new vasm/vlink and a resolution of the upper case files in debug that can mess with the breakpoint resolution, and maybe the last version of vscode has some new behavior. Yes there is something with the breakpoints in 0.18 on windows (works on osx my dev platform). I'm still digging... |
||
21 October 2019, 00:09 | #108 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
@Antiriad_UK and @Hannibal
Could you please try this fix ? https://github.com/prb28/vscode-amig...indows_x64.zip It was a bug in my fs-uae modification in release mode. The -O2 optimization of GCC added some strange behavior on my poorly coded C code. Sorry for the trouble. |
21 October 2019, 00:21 | #109 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
|
|
21 October 2019, 00:25 | #110 |
OCS forever!
Join Date: Mar 2019
Location: Birmingham, UK
Posts: 418
|
Yeah just tested, it was the same. Sorry!
|
21 October 2019, 00:45 | #111 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
|
21 October 2019, 18:42 | #112 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
0.18.1 is out with new binaries for windows and osx.
@Antiriad_UK: you issue should be fixed now! Thanks for testing! |
21 October 2019, 19:21 | #113 |
OCS forever!
Join Date: Mar 2019
Location: Birmingham, UK
Posts: 418
|
|
21 October 2019, 19:50 | #114 |
Registered User
Join Date: Dec 2016
Location: England
Posts: 87
|
Will these help with https://github.com/prb28/vscode-amiga-gcc-example as well?
Be cool to have a debugging IDE for bebbo's GCC. |
21 October 2019, 21:44 | #115 | |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
It uses another way to build and debug. It's the C/C++ extension that does the most part of the work and gdbserver is connected to a gdb instance in your host system. I can try to help you to make it work (pm me if you want). |
|
21 October 2019, 21:44 | #116 |
Registered User
Join Date: May 2015
Location: Kirkland, Washington, USA
Posts: 56
|
I tried 0.18.1, but I still saw the same problem. Is there anything else I have to do other than let VS.Code install the update, and then restarting VS.Code? Do I need to restart my PC? clean and recompile? download a new example repo?
|
21 October 2019, 21:47 | #117 |
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Yes you need to get the new bin directory: https://github.com/prb28/vscode-amig...indows_x64.zip
For you bug the fix in the fs-uae binary executable. |
22 October 2019, 08:03 | #118 |
Registered User
Join Date: May 2015
Location: Kirkland, Washington, USA
Posts: 56
|
after updating the bin files it works perfectly, thank you for fixing it so quickly
|
22 October 2019, 10:00 | #119 |
ex. demoscener "Bigmama"
Join Date: Jun 2012
Location: Fyn / Denmark
Posts: 1,637
|
I have noticed 2 issues in 0.18 (windows 10) with the debug configuration using the example workspace:
1) The output binary (fs-uae\hd0\gencop) is not updated when pressing start, so it fires up an old version - when using the run configuration it's ok. 2) When starting, the emulator runs "twice" before returning to the ide (i.e. after clicking lmb to exit gencop, it reboots and runs gencop, and I have to click lbm again). Maybe it's related to 1)?. I will try 0.18.1 and see if it helps. Edit: I still have these 2 issues with 0.18.1 of the extension and the binaries. I've added debug output and fs-uae log. Last edited by hooverphonique; 22 October 2019 at 10:19. |
22 October 2019, 10:22 | #120 | ||
Registered User
Join Date: May 2018
Location: France
Posts: 246
|
Quote:
Code:
"buildWorkspace":true Quote:
In Run mode there is no injection so the binary is launched by the Startup-Sequence.In the fs-uae Debug mode the binary is injected in fs-uae at initialization before the Startup-Sequence started. So when it's done the normal amiga emulation start with a startup-sequence and re-runs the gencop binary. If you don't want it in debug, remove the gencop line in Startup-Sequence file and keep UAEquit call (to have a gentle exit). |
||
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
assembly code to test for assign (2.0+) | jotd | Coders. System | 2 | 27 December 2017 23:16 |
very basic C/ASM/Visual Studio hand holding | Sephnroth | Coders. C/C++ | 2 | 08 March 2016 20:15 |
Amiga Audio/Visual | KhneFr | request.Other | 6 | 03 January 2015 10:25 |
Profiling WinUAE with Visual Studio 2013 | mark_k | support.WinUAE | 3 | 14 January 2014 20:26 |
amiga visual editor | thinlega | request.Apps | 1 | 22 January 2003 15:48 |
|
|