I am seeking assistance on ResearchGate for debugging a Fortran program using gdb. The program consists of multiple subroutines written in different modules. Whenever I attempt to step into one of the subroutines to examine the underlying calculations, gdb encounters the following error: "Thread 1 hit Breakpoint 1, hardening::hardmodel10 (iphase=1, nslip=12, temp=298, dtime=0.0099999997764825821, g12=79800, burgerv=..., totgammasum=8.3999999999999995e-05, gammadot=..., pdot=0, gammadot_slip=..., gammadot_climb=..., absrss=..., signrss=..., rss=..., nidot_climb=..., didot_climb=..., climbmodel=1, climbparam=..., hardeningmodel=1, hardeningparam=..., hintmat1=..., hintmat2=..., tauc_t=..., loop_t=..., rhomobile_t=..., rhoimmobile_t=..., rhototal_t=..., ni_t=..., di_t=..., drhomobile=..., drhoimmobile=..., dni=..., ddi=..., dloop=...) at ../UMAT/hardening.f:795" The following error message is displayed: "../../gdb-10.2/gdb/gdbtypes.h:527: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] ../../gdb-10.2/gdb/gdbtypes.h:527: internal-error: LONGEST dynamic_prop::const_val() const: Assertion `m_kind == PROP_CONST' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) [answered Y; input not from terminal]." I would greatly appreciate any assistance in resolving this issue.
This might be your problem... FORTRAN is different from most other programming languages in that all parameters are passed by reference (pointers). This includes constants (e.g., pi or 298° and even 0.0). To prevent changing the value of pi or zero (yes, it is possible in FORTRAN to change zero) modern compilers have the option to place constraints on some variables passed by reference. If you try to pass something like T=298 call sub1(T) and it croaks, try call sub1(298.) Check the documentation for the library you are using. This would be consistent with the message, "Assertion `m_kind == PROP_CONST' failed"
- Badges
- Science topic