Uploaded image for project: 'Qt Creator'
  1. Qt Creator
  2. QTCREATORBUG-22976

Fortran strings are displayed as <not accessible> and <no such value> in Locals and Expressions View

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Not Evaluated
    • Resolution: Done
    • Affects Version/s: Qt Creator 4.9.0
    • Component/s: Debugger
    • Labels:
      None
    • Environment:
      QtCreator on CentOS 7 in docker container on Windows 7.
    • Platform/s:
      Linux/X11
    • Commits:
      89a36c72322a61761e24d69e2645b0b1d5fd822c (qt-creator/qt-creator/4.10)

      Description

      When debugging a fortran executable strings are displayed as <not accessible> and <no such value> in Locals and Expressions View. See attachments.

      After reading the Python scripts which reformat the variables I made the following change in the file qtcreator-4.9.0/share/qtcreator/debugger/dumper.py. It seems to work now. See attachments.

      Before

      2811         if typeobj.code == TypeCodeFortranString:
      2812             data = self.value.data()
      2813             self.putValue(data, 'latin1', 1)
      2814             self.putType(typeobj)
      2815
      

      After

      2811         if typeobj.code == TypeCodeFortranString:
      2812             data = value.data()
      2813             self.putValue(self.hexencode(data), 'latin1', 1)
      2814             self.putNumChild(0)
      2815             self.putType(typeobj)
      2816             return
      

      What can I do to get this changes upstream?

      Greetings

      Toby

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            hjk hjk
            Reporter:
            trh Tobias Henle
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes