m68k-amigaos-gdb

[Warty]

Originally Posted by bebbo

The installation failure is not related to that minor issue. Workaround:

Install 2019-12, install Amiga-CDT and perform an update -> you get 2020-06.

Thanks Bebbo! It works like a charm now. I wrote a game without anything like this, with just VBCC, and it was pretty darn painful. Now I'm all juiced up to start a new project. I've got a bad feeling about this C128 game I've been working on for the past 6 months, which is currently at 95% complete...

Thanks for the cross chain, and also for the debugger. Seriously, magic.

[activist]

Originally Posted by bebbo

sounds dumb... but...create a .gdbinit file in your home folder

Have you an example .gdbinit file ?

Seems to work ok on command line.

e.g. On the target (amiga), type 'bgdbserver helloworld' I get 'Running GDB server on port 2345'.
Then on host (windows 7 64) type 'target remote localhost:2345'. Seems to connect. Says 'Remote debugging using localhost:2345'
At this point I can set break point ..b 18.
Or just type 'cont'.
I can then see it executing successfully on target.

So that's all fine. But Eclipse. Not sure..Windows version at least anyway.
A quick google on bing for gcc Eclipse stuck 'Launching Debug: (91%)' Starting Program: Configuring GDB seems a well known issue.


Also, no joy at all port 514.

e.g. on target if I type 'bgdbserver' I get 'Starting RSH server on port 514'.
on windows host cmdline type:
'bgdbserver helloworld'
then
'target remote localhost:514'
but just times out.

[bebbo]

Originally Posted by activist

Have you an example .gdbinit file ?

Seems to work ok on command line.

e.g. On the target (amiga), type 'bgdbserver helloworld' I get 'Running GDB server on port 2345'.
Then on host (windows 7 64) type 'target remote localhost:2345'. Seems to connect. Says 'Remote debugging using localhost:2345'
At this point I can set break point ..b 18.
Or just type 'cont'.
I can then see it executing successfully on target.

So that's all fine. But Eclipse. Not sure..Windows version at least anyway.
A quick google on bing for gcc Eclipse stuck 'Launching Debug: (91%)' Starting Program: Configuring GDB seems a well known issue.


Also, no joy at all port 514.

e.g. on target if I type 'bgdbserver' I get 'Starting RSH server on port 514'.
on windows host cmdline type:
'bgdbserver helloworld'
then
'target remote localhost:514'
but just times out.

an empty file should do it.


plus you have to configure that file in Eclipse with abolute path
in the Debug settings what gdbinit file to use. Set it in the preferences and it's there in new debug configurations.


I can debug with Eclipse 202006 in Windows now