@nunesgh

If you're on Windows or a Mac, you can ignore this! However, if on Linux...

For quite a long time now there have been some Linux users who get lots of SIGSEGV (signal 11) like yours on various applications, including the WCG HSTB program (and SCC until more recently). Those applications had been built with older libraries and changes to Linux kernels had an effect on some common optimized system-level functions such as getting the current time. In the worst case (completely disabled call mechanism), the calls resulted in SIGSEGV...

If you search the forums for vsyscall, there are quite a few threads on the subject; I'll point you at a reply by hchc which includes the work-around if this is your issue.

A newer version of the SCC application uses a library version that should work on both older and newer systems; somewhere in the first of the two threads linked to in hchc's post, uplinger explains why it's unlikely HSTB will be rebuilt in the near future.

Hope this helps - Al.