Am going to work on the source code problem now that I am home. I keep thinking I am missing an option to activate.flynn wrote:I do not use the editor with Code::Blocks, just do the project to allow the debugger.
I have notice there is no source code inside your project, there is may be a problem here.
I have not tried an ASM only project, but I use C/ASM ones.
Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Moderator: a31chris
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
I do not recognize the traditional setup I have at my side. I will re-read the document to be sure no information is missing.
Also, in your picture, the project doesn't have a source file. This situation has to be solved too.
Also, in your picture, the project doesn't have a source file. This situation has to be solved too.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Yeah that's the big issue I have been trying to solve. Am going to try to delete everything tonight and start from scratch make sure I did not miss anything.flynn wrote:I do not recognize the traditional setup I have at my side. I will re-read the document to be sure no information is missing.
Also, in your picture, the project doesn't have a source file. This situation has to be solved too.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
I've got to this point however how do I do step 6?5. Fill the debug fields in accordance with your project directories
a. The “Release” field is up to you to be filled or not
6. Once completed, fill your project with a least one source file
It just goes to the gui workspace. I don't know how to fill my project with at 'at least one source file'.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Does it matter if we use forward slashes or backward slashes in the debugger arguments fields?
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Good question; yes, this is here. I think I need to clarify this in the documentation.a31chris wrote:Is this where I 'add files" I pointed it at the Jag c source code. Let's see what happens.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
I have only used the '/' character (like displayed in the screenshot in the document); i do not know if the '\' will work.a31chris wrote:Does it matter if we use forward slashes or backward slashes in the debugger arguments fields?
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
GDB will display automatically the source code pointed in the application debug information.
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Well I'm getting closer to something but nothing is being displayed on the screen. Hmm more kinks to work out.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
flynn wrote:GDB will display automatically the source code pointed in the application debug information.
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
Code: Select all
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
c:\stuff\Skunkboard\Source\GDB>jcp -r
jcp v02.03.01 built on Oct 14 2009
Resetting jaguar...
c:\stuff\Skunkboard\Source\GDB>jserve
Installed EZ-HOST stub: 60 scan codes sent
COFF File: Skip 168 bytes, base addr is 2000, sending 2971 bytes...Send a block
Installed!
Establishing contact with Jaguar stub...Connected!
Waiting on localhost:4567...Connected! Logging to jdb.log.
Installed EZ-HOST stub: 60 scan codes sent
Connected to existing Jaguar stub...
Write to Jaguar address 00002C00, 180 bytes
Got command qSupported:multiprocess+;qRelocInsn+#
Unknown command 'q' (0x71)
Reply:
Got command Hg0#
Unknown command 'H' (0x48)
Reply:
Got command ?#
Signal: 0x05
Reply: S05
Got command Hc-1#
Unknown command 'H' (0x48)
Reply:
Got command qC#
Unknown command 'q' (0x71)
Reply:
Got command qAttached#
Unknown command 'q' (0x71)
Reply:
Got command g#
Read Registers
Reply: 0000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000001ffff80000200000004000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000
Got command qTStatus#
Unknown command 'q' (0x71)
Reply:
Got command qTStatus#
Unknown command 'q' (0x71)
Reply:
Got command qTStatus#
Unknown command 'q' (0x71)
Reply:
Got command vCont?#
Unknown command 'v' (0x76)
Reply:
Got command Hc0#
Unknown command 'H' (0x48)
Reply:
Got command c#
Wait while Running....
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Do your crt0.s is correct?
For the disasm, you can also turn 'on' the Disassembly window. This window will display automatically the disassembly.
For the GDB debugger setup, could you try to have '/' instead to use the '\' in the arguments line and in his initialization commands.
You also should update your jserve, the one from Tursi or the new one done by me.
For the disasm, you can also turn 'on' the Disassembly window. This window will display automatically the disassembly.
For the GDB debugger setup, could you try to have '/' instead to use the '\' in the arguments line and in his initialization commands.
You also should update your jserve, the one from Tursi or the new one done by me.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Where is that at? You're just points to File: c:/Projects/Jagl/examples/debug/spin.elf.bin <<--- this seems like a binary name. Is this a typo? Should I point it at a source code instead of a binary file?flynn wrote:GDB will display automatically the source code pointed in the application debug information.
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
jserve was just downloaded from Tursi's. It should be the latest.
Will change to forward slashes.
Will change to forward slashes.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
No, I was just telling that if GDB needs to show a source C file due to a breakpoint, it will use the debug information available in the bin file. So, it will display the source file in accordance There are no typos.a31chris wrote:Where is that at? You're just points to File: c:/Projects/Jagl/examples/debug/spin.elf.bin <<--- this seems like a binary name. Is this a typo? Should I point it at a source code instead of a binary file?flynn wrote:GDB will display automatically the source code pointed in the application debug information.
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
ok taking a break for now. Am not sure what is going on. Let me think on it.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
jserve, the version you have is quite old (2008) and doesn't have the communication fixes Tursi did after this release. I will recommend either to use:a31chris wrote:jserve was just downloaded from Tursi's. It should be the latest.
Will change to forward slashes.
1) The jserve updated version from 2013.
2) My version of jserve
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Well for me it's not automatically listing the source file. I have to point it at it. Which is kinda working. And using the command line at the bottom it seems to want to behave but still won't run the program to completion. Grrrr....flynn wrote:No, I was just telling that if GDB needs to show a source C file due to a breakpoint, it will use the debug information available in the bin file. So, it will display the source file in accordance There are no typos.a31chris wrote:Where is that at? You're just points to File: c:/Projects/Jagl/examples/debug/spin.elf.bin <<--- this seems like a binary name. Is this a typo? Should I point it at a source code instead of a binary file?flynn wrote:GDB will display automatically the source code pointed in the application debug information.
I also do not understand from where this hellodebug.exe comes from, you already have a .bin (I guess this .bin is your Jaguar application).
Could you display the jserve window and the GDB debugger information you have entered during your setup?
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
How can you tell what Jserve version I am using? I can't see a time stamp on anything except jcp in any of the command windows.flynn wrote:jserve, the version you have is quite old (2008) and doesn't have the communication fixes Tursi did after this release. I will recommend either to use:a31chris wrote:jserve was just downloaded from Tursi's. It should be the latest.
Will change to forward slashes.
1) The jserve updated version from 2013.
2) My version of jserve
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
I see this line displayed :a31chris wrote:How can you tell what Jserve version I am using? I can't see a time stamp on anything except jcp in any of the command windows.flynn wrote:jserve, the version you have is quite old (2008) and doesn't have the communication fixes Tursi did after this release. I will recommend either to use:a31chris wrote:jserve was just downloaded from Tursi's. It should be the latest.
Will change to forward slashes.
1) The jserve updated version from 2013.
2) My version of jserve
"COFF File: Skip 168 bytes, base addr is 2000, sending 2971 bytes...Send a block
Installed!"
There is a missing information in the line, before the "Send a block". This information was later added in the version from 2013.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
ok I redownloaded from Tursi's site. Overwrote everything. Now I get 'Jserve is not a valid win32 application.' :/
Taking a break.
Taking a break.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
I am going to have to learn to fix the makefiles and compile these myself on my system.
I am going to take a paranoid guess since I also got the same thing with the 32bit 1.0.18 version of smac binary you sent me that M$VS is doing something that is making their builds incompatible with older 32 bit OS's like mine.
Paranoid logic but there it is.
I am going to take a paranoid guess since I also got the same thing with the 32bit 1.0.18 version of smac binary you sent me that M$VS is doing something that is making their builds incompatible with older 32 bit OS's like mine.
Paranoid logic but there it is.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
May be your Windows system doesn't have a Visual C++ 2013 redistribute package?a31chris wrote:I am going to have to learn to fix the makefiles and compile these myself on my system.
I am going to take a paranoid guess since I also got the same thing with the 32bit 1.0.18 version of smac binary you sent me that M$VS is doing something that is making their builds incompatible with older 32 bit OS's like mine.
Paranoid logic but there it is.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Perhaps. I will look into it.
http://blogs.msdn.com/b/vcblog/archive/ ... 20645.aspxWe recently announced the Visual Studio 2012 product lineup and platform support, and as a part of this announcement we mentioned that we were evaluating options for enabling C++ developers to build applications in Visual Studio 2012 that run on Windows XP without requiring side-by-side installation of Visual Studio 2010. Today I would like to share more details about this capability.
Background
The C++ runtime and libraries that accompany Visual Studio 2012 contain dependencies on several Windows API functions that exist only on Windows Vista and higher versions of the OS. This means that applications built with Visual Studio 2012’s C++ compiler will fail to load and execute on Windows XP. Developers wishing to target Windows XP can use Visual Studio’s C++ multi-targeting feature, which enables the use of the Visual Studio 2010 compiler from within the new IDE. Multi-targeting enables developers to take advantage of the new features of the IDE without migrating projects to the new compiler or to use the Visual Studio 2010 compiler to build applications that target Windows XP.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Alright installed the redistributable. Will try this again in a couple days. Or now. 

What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
ok still same error after reboot. I am going to have to recompile the damn thing. Thanks M$.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Sorry about this. You can also use Visual C++ 13 to recompile the stuff. It is free to use from MS.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Yeah I stopped using VS because it ate all my setpaths. And doesn't it want Windows Vista and higher anyway?flynn wrote:Sorry about this. You can also use Visual C++ 13 to recompile the stuff. It is free to use from MS.
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
VS C++ 2013 is supported from Windows XP to Windows 8.1. Windows Vista included.a31chris wrote:And doesn't it want Windows Vista and higher anyway?
I use Windows 7 Home 64 bits.
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Code: Select all
c:\stuff\Skunkboard\Source\GDB>jserve
jserve v1.1a - Win32 - (Feb 17 2015)
Installed EZ-HOST stub: 60 scan codes sent
COFF File: Skip 168 bytes, base addr is 2000, sending 2971 bytes...poll = 5
Send a block
Installed!
Establishing contact with Jaguar stub...Connected!
Waiting on localhost:4567... Connected!
Installed EZ-HOST stub: 60 scan codes sent
Connected to existing Jaguar stub...
Assertion failed: !(erno = fopen_s(&flog, jdblogFile, "w")), file c:\projects\sk
unkboard\gdb\jserve\jserve.cpp, line 212
What came after the Jaguar was the PS1 which for all it's greatness, ushered in corporate development and with it the bleached, repetitive, bland titles which for the most part we're still playing today. - David Wightman
Re: Visual GUI: Debug w/Skunkboard, GDB & Code::Blocks(M68k)
Have you tried to run jserve in Administrator mode?a31chris wrote:Once I launched codeblocks debugging the above happened. I however was attempting to use the old jcp. That may have been the problem.Code: Select all
c:\stuff\Skunkboard\Source\GDB>jserve jserve v1.1a - Win32 - (Feb 17 2015) Installed EZ-HOST stub: 60 scan codes sent COFF File: Skip 168 bytes, base addr is 2000, sending 2971 bytes...poll = 5 Send a block Installed! Establishing contact with Jaguar stub...Connected! Waiting on localhost:4567... Connected! Installed EZ-HOST stub: 60 scan codes sent Connected to existing Jaguar stub... Assertion failed: !(erno = fopen_s(&flog, jdblogFile, "w")), file c:\projects\sk unkboard\gdb\jserve\jserve.cpp, line 212
The error is about the log creation file, you can also launch jserve with the -nolog parameter, it won't generate a log file.
In the meantime, I will try to reproduce your problem.