Скачать или смотреть Troubleshooting Fortran: How to Add a Watchpoint to a COMMON Block

Discover how to effectively monitor `COMMON` block variables in Fortran using gdb. This guide provides a detailed solution, steps, and examples for debugging divide-by-zero issues.
---
This video is based on the question https://stackoverflow.com/q/72130301/ asked by the user 'Frank' ( https://stackoverflow.com/u/4437892/ ) and on the answer https://stackoverflow.com/a/72187994/ provided by the user 'Frank' ( https://stackoverflow.com/u/4437892/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Can I add a watch to a COMMON block?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Fortran: How to Add a Watchpoint to a COMMON Block

When working with older Fortran code, especially extensive and poorly documented systems, debugging can become a daunting task. One frequent issue that programmers encounter is the dreaded divide-by-zero error, which can occur for various reasons. In this guide, we will explore a specific scenario involving COMMON blocks in Fortran and how to effectively set watchpoints in gdb to identify when and where certain variables are being modified.

Understanding the Problem

Imagine you are inheriting a large, antiquated piece of Fortran code with complex interdependencies, and you stumble upon a segment causing a runtime divide-by-zero error. For instance, take the following subroutine:

[[See Video to Reveal this Text or Code Snippet]]

In this subroutine, the division in the last line can potentially lead to a divide-by-zero error if the variables involved (specifically r(6), r(8), z(6), z(8)) do not hold valid values. The root of the issue lies in the fact that r(8) equals r(6) and z(8) equals z(6), leading to a situation where the logarithm of a non-positive number results in an error.

Your challenge is compounded by the complexity of the codebase where the variables r and z are defined in a COMMON block, and you have no clear visibility on where these variables are being assigned values.

The Search for Variable Assignments

You might try using grep to comb through the codebase looking for where r(8) and z(8) are being set, but to no avail. Even when inspecting their values in gdb, they appear valid—simply not in the correct state they need to be for your calculations.

Solution: Setting a Watchpoint

After some analysis, a practical solution arises: use a watchpoint in gdb to monitor changes to the memory address of your COMMON block variables.

Why Use Watchpoints?

Watchpoints are powerful in debugging because they allow you to monitor specific memory addresses. Since variables in COMMON blocks have static memory allocation, their addresses remain consistent throughout the execution of the program. Thus, you can set a watchpoint to notify you when any referenced variable is modified.

Steps to Set a Watchpoint in gdb

Run Your Program in gdb: Begin your debugging session as you normally would.

[[See Video to Reveal this Text or Code Snippet]]

Execute the Program: Start the execution to reach the point where the divide-by-zero may occur.

[[See Video to Reveal this Text or Code Snippet]]

Identify Address of COMMON Variable: When the error occurs, use the command to get the address of the variable of interest (e.g., r(8)).

[[See Video to Reveal this Text or Code Snippet]]

This might output something like:

[[See Video to Reveal this Text or Code Snippet]]

Set the Watchpoint: Use the address obtained in the previous step to set a watchpoint on that variable.

[[See Video to Reveal this Text or Code Snippet]]

The output will confirm that the watchpoint has been successfully set.

Rerun the Program: You will need to restart your program to start tracking changes. If prompted, confirm to start the program from the beginning.

[[See Video to Reveal this Text or Code Snippet]]

Monitor Changes: When your program executes and the value at r(8) changes, gdb will inform you:

[[See Video to Reveal this Text or Code Snippet]]

Confirming Variable Assignments

Using the backtrace command, you can see where r(8) was modified, confirming the point in your code responsible for assigning it a value.

[[See Video to Reveal this Text or Code Snippet]]

This will help you uncover the root cause of the problem and address the divide-by-zero error effectively.

Conclusion

Understanding and effectively using gdb t