using DSS (Debug Server Scripting) generic loader 'loadti' unit testing is performed in a Linux environment.
Consecutive automation tests are performed sequentially.
Often Java "Segmentation fault" occurs at some point, mostly after several preceeding 'loadti'-loaded tests performed well.
Once the failure occurs, it remains there at the same test (even on test-repetition).
# An unexpected error has been detected by Java Runtime Environment:
# SIGBUS (0x7) at pc=0xf7e484fc, pid=46945, tid=2916301680
# Java VM: Java HotSpot(TM) Server VM (11.3-b02 mixed mode linux-x86)
# Problematic frame:
# C [libc.so.6+0x1384fc]
Java that is in use is the one that comes with CCS5.5: java version "1.6.0_13"
We have already discovered the cause for that behaviour:
- 'loadti' caches loaded .out files in the following folder: /dev/shm/
After tests get performed and 'loadtti' terminates, most of the cached objects remain in this as
- With a time this amount of data gets too large causing the Java error.
Manual emptying this folder helps.
Finally the question:
- How is it possible to control what happens with the content of the folder /dev/shm/ ?