#1 workaround to make debugging of ECUT build possible

[Helmut]

Problem: can not debug using ECUT connector, see ID: 2666058 (https://sourceforge.net/tracker/index.php?func=detail&aid=2666058&group_id=236439&atid=1100279)
Workaround (for me):
- create a new build configuration (ECUTDebug), copied from the ECUT build configuration (ECUTTest), do not forget to rename the build artefact, e.g. to ECUTDebug.exe
- additionally define a symbol ECUTDEBUGWORKAROUND in this build configuration
- use ECUTDEBUGWORKAROUND to comment out the client connect in EcutClient.cpp, since there won't be any ECUT server side available if run
as a normal C/C++ application
- set up a debug configuration to be able to easily run the debug session as a standard C/C++ application
- now build your binary with the new build configuration, set your breakpoints e.g. on your failing tests, start the debug session and have fun ;-)

The following patch is just a quick workaround to be able to suppress the connection to the ECUT server, otherwise you cannot run the ECUT build as standard C/C++ application successfully. Maybe it should be made available by an additional command line switch (e.g. -noconnect). Nevertheless in my opinion we should make the ECUT build itself debuggable ASAP, in which case this patch will become redundant.

[Helmut]

add #ifdef ECUTDEBUGWORKAROUND

[Helmut]

Sorry the patch file does not apply without probs! Use ecutdebugworkaround2.patch to patch EcutClient.cpp revision 1.12

[Helmut]

appy against net.sf.ecut.cppunit/lib/EcutClient.cpp revision 1.12

[Gerhard H. Leonhartsberger]

Do you have some pointers for making ECUTClient debuggable?

Gerhard