View previous topic :: View next topic |
Author |
Message |
StamK
Joined: 12 Oct 2016 Posts: 159
|
Posted: Fri Nov 27, 2020 1:13 am Post subject: Maximum size of object covered by hardware breakpoint |
|
|
In 32bit debugger no issue.
In 64bit, when trying to set a write break (in this case a string member of a derived type), I am getting the following error
The maximum sizee of object that can be covered by a hardware breakpoint is 32-bytes. Seems to be fine for numerical members of the derived type. |
|
Back to top |
|
|
mecej4
Joined: 31 Oct 2006 Posts: 1886
|
Posted: Fri Nov 27, 2020 5:26 am Post subject: |
|
|
Please show the declaration(s) of the derived type(s). |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
Posted: Fri Nov 27, 2020 10:03 am Post subject: |
|
|
The error is correct in that the maximum size is 32-bytes -- and the real value is less as sdbg64 uses some of these for things like step-out.
Does it work in 32-bit mode -- i.e. does it break when required? |
|
Back to top |
|
|
StamK
Joined: 12 Oct 2016 Posts: 159
|
Posted: Fri Nov 27, 2020 11:41 am Post subject: |
|
|
Code: |
!ftn95$free
MODULE TYPES
TYPE MITM
SEQUENCE
CHARACTER*260 :: NAME
END TYPE MITM
CONTAINS
SUBROUTINE MI_Init (MI)
TYPE (MITM), POINTER :: MI
MI%NAME = ' ' !set a write break on variable breakpoint here
END SUBROUTINE
END MODULE TYPES
program testmit
USE TYPES
TYPE (MITM), POINTER :: MIT=>Null()
ALLOCATE (MIT, stat=IST); call mi_init(MIT)
end program
|
|
|
Back to top |
|
|
StamK
Joined: 12 Oct 2016 Posts: 159
|
Posted: Thu Dec 03, 2020 10:41 am Post subject: |
|
|
Has anyone confirmed the issue with the above code sample? Thanks |
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Thu Dec 03, 2020 3:58 pm Post subject: |
|
|
I can cofirm the behaviour mentioned by StamK for
ftn95 version 8.63.0 and sdbg64 version 8.62a
Regards
Dietmar |
|
Back to top |
|
|
silverfrost Site Admin
Joined: 29 Nov 2006 Posts: 191 Location: Manchester
|
Posted: Thu Dec 03, 2020 11:31 pm Post subject: |
|
|
There is a new sdbg64 available that fixes this issue. |
|
Back to top |
|
|
StamK
Joined: 12 Oct 2016 Posts: 159
|
Posted: Fri Dec 04, 2020 12:45 am Post subject: |
|
|
I can confirm this is now fixed, thanks |
|
Back to top |
|
|
|