[cdt-dev] Neon.2 on Windows: GNU ARM Eclipse debug plug-ins do not start

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] Neon.2 on Windows: GNU ARM Eclipse debug plug-ins do not start

From: Liviu Ionescu <ilg@xxxxxxxxxx>
Date: Sun, 25 Dec 2016 10:25:17 +0200
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>

The problem seems Windows specific, the macOS version looks ok.


The first report came for OpenOCD on Windows (https://github.com/gnuarmeclipse/plug-ins/issues/156), but I checked and the J-Link plug-in is also affected.

The behaviour is similar, the plug-ins hang late in the startup sequence. There are no exceptions in the logs (my test environment is Win8 x64 in a VM).


Regards,

Liviu

Prev by Date: Re: [cdt-dev] new console incompatibilities?
Next by Date: [cdt-dev] [aeri] Weekly Problem Digest for C/C++ Development Tools
Previous by thread: [cdt-dev] new console incompatibilities?
Next by thread: [cdt-dev] Help needed from a CDT developer with a Mac
Index(es):
- Date
- Thread

Breadcrumbs