Breeze Trace

Breeze use case studies

Analysing a large trace

A CAD engineer customer of an EDA vendor ran a trace in Breeze but had to stop it with “kill -9” because it appeared to have hung.

Comparing commands on different machines

A customer couldn’t work out why a program stopped working on one of their servers, but not the others.

Use as customer service

The customer of a Breeze user kept seeing a tool error that indicated that the wrong arguments were being passed into the tool.

Debugging a slow software build

A software engineer found that a software build was taking too long and wanted to use Breeze to find out why.

Optimising file system use

Some of a customer’s programs were storing temporary files on remote areas of the file system, hogging the network.

Hardware configuration

A customer found that in any new login session on any machine, either at the console or via VNC, he couldn’t type anything in.

Library not found

A customer was running a complex build and they got a GCC ‘library not found’ error message.

Resolving library dependency problems

A tool wouldn’t start at the customer’s site because of library problems.

Optimising file system use

Some of a customer’s programs were storing temporary files on remote areas of the file system, hogging the network.

Solving build configuration mistakes

When a software build is run in parallel on multiple machines the file system gets overloaded and the scaling performance drops.

Solving conflicting libraries

A customer had the issue of conflicting libraries when their product was running at client side.

Tracing scripts

A customer was running a complex simulation controlled by an in-house scripted flow and getting an error that didn’t make sense.

Trouble shooting performance issues

A customer had problems one day when all their applications slowed down.