Debugging FESA binaries via Console

In order to simplify thing, a script with predefined application-arguments is provided to minimize typing-effort when starting gdb.

Copy the script into the same folder where the instantiation-file of your deployment-unit is located and give execution-right to the script:

chmod +x startScriptCluster.sh

Now modify the first 4 lines of the script according to your needs (all other lines should be fine)
CPU=i686
FESA_VERSION=1.0.0
DU_NAME=NameOfDeployUnit
BINARY_NAME=${DU_NAME}_M-0.1.0

and start the script with the application-argument "gdb":

./startScriptCluster.sh gdb

If you dont provide the application-argument, the fesa-binary will start as usual.
I Attachment Action Size Date Who Comment
startScriptCluster.shsh startScriptCluster.sh manage 1 K 12 Nov 2013 - 14:01 AlexanderSchwinn Script to auto-start a gdb-session for a fesa-binary
Topic revision: r2 - 13 Nov 2013, AlexanderSchwinn
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback