Bug 507429 - The problem with the launch SEGGER J-Link GDB Server
Summary: The problem with the launch SEGGER J-Link GDB Server
Status: CLOSED NOT_ECLIPSE
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 9.1.0   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Doug Schaefer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-13 02:25 EST by Evgeni Sosnin CLA
Modified: 2019-09-22 15:14 EDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Evgeni Sosnin CLA 2016-11-13 02:25:17 EST 
Im use Gnu ARM plugin
There is a problem with the launch  SEGGER J-Link GDB Server V5.12f 
Window Progress show 99% launching: Configuring GDB 

in version Eclipse C/C++ Development Tools Version: 9.0.0.201606062011 project work debug fine

-- Configuration Details --
Product: Eclipse 4.7.0.20161103-0600 (org.eclipse.epp.package.cpp.product)Installed Features:
 org.eclipse.platform 4.7.0.v20161027-1055
Comment 1 Ivan Pajuelo CLA 2017-01-06 13:51:59 EST 
Same problem here.
Seems an old CDT problem returned to 9.1.0
Evgeni Sosnin. You can run JLinkGDBServerCL by yourself everytime before start a debug session.
I use it with these command line parameters "-if swd -device MKL27Z256xxx4 -endian little -speed 1000 -port 2331 -swoport 2332 -telnetport 2333 -vd -ir -localhostonly 1 -singlerun -strict -timeout 0 -nogui"
(Remember to use your own configuration. target, iinterface and endianess)
You can also use the GUI version with the same parameters and don't need to start it every time.
Hope this help while the problem is not solved AGAIN (I think this problem is randomly appearing since 2014 or before)
Comment 2 Marc Khouzam CLA 2017-01-30 09:30:40 EST 
We have experienced a couple of bugs related to GDB 7.12 with the CDT 9.2 release.

Can you provide the gdb traces to help us debug?
 https://wiki.eclipse.org/CDT/User/FAQ#I.27ve_been_asked_for_.27gdb_traces.27.2C_where_can_I_find_them.3F
Comment 3 Liviu Ionescu CLA 2017-01-30 13:20:39 EST 
Evgheni & Ivan,

Could you retest with the GNU ARM Eclipse plug-ins beta version? 

It is available from:

    http://gnuarmeclipse.sourceforge.net/updates-test

This version should start the J-Link GDB server and the GDB 7.12 client properly, run the debug session, single step, halt at breakpoints, but fail to suspend or terminate the session (this is anther bug in CDT that I have no workaround for).

Liviu
Comment 4 John Dallaway CLA 2019-09-22 10:07:21 EDT 
As far as I can tell, the reported issue relates to the GNU MCU Eclipse plugins (not CDT). I observe no issues with debug sessions using the SEGGER GDB Server when launched using the CDT "GDB Hardware Debugging" launch configuration type.

If there is something that I have missed, please re-open this ticket.
Comment 5 Liviu Ionescu CLA 2019-09-22 15:14:15 EDT 
I also do not observe any issues with the current versions of the toolchains and of GNU MCU Eclipse, so I concur with closing this ticket.