Now we can actually go and explore the cause effect chain.

In producing such a cause effect chain automatically is your homework.

What we get in here is actually an entire cause effect chain.

When we're debugging now, we need to identify this cause effect chain not only do we need to identify but we also need to break the cause effect chain.

What Sherlock Holmes reconstructs in his reasoning over here is a cause effect chain.

Cause and effect.

Cause and effect.

This cause effect chain may or may not include the infected values, but frequently it does.

Having such a cause effect chain and getting it automatically sounds like a great promise for debugging

If we can break this cause effect chain from defect to failure, then we're done with debugging.

So if there's a failure, we can always fix it by following back the cause effect chain.

Cause and effect. Au revoir.

Cause and effect, my love.

Karma Cause and effect (Birds chirping)

So tracing back the cause effect chain can be much, much more complicated that it is in this simple picture.

Every cause produces more than one effect.

Cause and effect react upon each other.

So, again, we have a chain of dependencies out going up here, up here, up here, up here, and you can also see this as a cause effect chain.

This cause effect chain is what you get when you apply delta debugging on state differences at various places during the execution.

The earlier you see an infection for instance, because an assertion fails, the shorter the cause effect chain, we need to investigate.

What you could get out of that is an automatic cause effect chain isolating the causes for different places during the program execution.

Because for every cause, there must be an effect.

An effect like this could cause earthquakes, tidal waves.

Right? The cause has to come before the effect.

It's cause and effect. Sorry, sir, this table is closed.

In other words, what we get is cause effect chain throughout the program, which explains how the failure came to be in all of this automatically.

This law of cause and effect also applies to our destiny.

Chain

The same cause does not always give rise to the same effect.

We need to study the cause and effect of the accident closely.

The longer the cause effect chain, that is the longer the time we have to cover, the more states we have to cover, the harder is to debug it.

Certificate chain

Getting the cause and the effect right makes all the difference in the world.

Derivative chain rule.

The chain rule.

Form a chain!

That's chain saws.

Chain saw, check.

Carbon chain c24.

Effect

Again, we're talking about outliers there's got to be some kind of cause and effect.

An actual cause assumes and changes as little as possible, but it changes the effect.

This mission was supposed to cause dissension in the region. It's had the opposite effect.

If the machine gets to the station it'll cause a chain reaction that'll vaporize the city's water supply.

In debugging, we also have such a cause effect chain from the defect to the infection that is, an error in the state and finally to the failure, which can be observed by a user.