[Al-Cambridge-UK]

Thank you for your reply, but I must apologise that I still don’t understand how these settings work.

I do not understand from your last comment “this configuration should not be used to build the project” how to start debugging without compiling.

I will summarise my requirements:

• I am using VisualGDB Classic Linux edition to cross-compile for ARM and debugging on a Raspberry Pi over network. This has worked successfully for a number of projects over the last year.
• I am developing a filter for CUPS printing, HelloCUPSFilter, and the difference here is that the executable will be started by another process. I am simulating this by calling the executable from within a command shell file, HelloCUPS.sh. My executable is deployed to the path /usr/lib/cups/filter. Initially my program merely prints the program arguments.
• The source files to debug are therefore on my Windows computer, not on the deployment machine, pi@192.168.0.216.

Your screenshot for Project settings does not show settings for “File synchronization”.

Your screenshot for Debug settings does not show settings for “Deploy main executable to” or “Deploy condition”.

Please provide clear instructions for all steps in the process, and please assume that while competent I do not have detailed knowledge of your product.

Thanks, Alasdair

[Al-Cambridge-UK]

I’m afraid that I don’t understand that last sentence.

I would be grateful for instructions to launch gdb on the target machine, please.

[Al-Cambridge-UK]

And here is the GDB Log…

VisualGDB is licensed to Alasdair Hayden-Wright at Synoptics Ltd
o21: gdbserver exited with code 255
at yy.j1()
at yy.w_2(DebugCustomizationSettings a)
at di.l2()
at VisualGDB.GDBDebugEngine.o(mk1 a, e b)

[Al-Cambridge-UK]

Here is the entirety of the HelloCUPSFilter program…

#include <stdio.h>

int main(int argc, char *argv[])
{
for( int i = 0; i < argc; i++ )
{
printf( “argv[%d]=%s\n”, i, argv[i] );
}

return -1;
}

[Author]

Posts