I have made some progress. I have tested from the J-Link command line and everything works as expected.

System Workbench now recognises the J-Link device, now my problem is that when I choose debug the most recently compiled binary (.elf) is loaded to my target and the program starts. Debugging is not enabled, the program continues to run and the debug window displays the following messages.

MyProgram GDB SEGGER J-Link Debugging
JLinkGDBServer
gdb
Semihosting and SWV

The Debugger console displays the following:
MyProgram GDB SEGGER J-Link Debugging ${cross_prefix}gdb${cross_suffix}(???)
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type “show copying”
and “show warranty” for details.
This GDB was configured as “x86_64-linux-gnu”.
Type “show configuration” for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type “help”.
Type “apropos word” to search for commands related to “word”.
Warning: the current language does not match this frame.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000000 in ?? ()

• stack smashing detected ***: gdb terminated

I am still looking for any suggestions.

Quite a bit of text disappeared when I posted that last message. There must be some formatting process I am unaware of. Any thing inside “left arrow” and “right arrow” is not shown.

(terminated)MyProgram GDB SEGGER J-Link Debugging
(terminated, exit value: 0)JLinkGDBServer
(terminated, exit value: -1)gdb
(terminated, exit value: 0)Semihosting and SWV

Changing the GDB Client Setup, executable path in the debugger configuration from ${cross_prefix}gdb${cross_suffix} to a direct path to the executable arm-none-eabi-gdb appears to have solved my issues.