Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28259

Memory map plugin fails when Linker Command FIle is not UTF-8 (Texas Instruments) (case 12990 Praqma)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • memory-map-plugin
    • None
    • jenkins 1.6.12, memory-map-plugin 1.02

      Steps to reproduce:

      • use a Linker command file that contains umlauts like öäü
      • save it as with this encoding: cp1252
      • run a build with jenkins
      • now you'll see that jenkins will fail, because it opens the command file as utf-8 and will fail to decode the umlauts

      Background:
      Texas Instruments C6000 Code generation tools Version 6.1.x can't even use utf-8 encoded linker command files, the linker will fail.

      Possible solutions:

      • add some magic to determine the command file encoding
      • let the user define the encoding
      • use the systems default encoding ( java:Charset.defaultCharset() )
      • try utf-8 and ascii (attached patch, low quality, just as a idea)

          [JENKINS-28259] Memory map plugin fails when Linker Command FIle is not UTF-8 (Texas Instruments) (case 12990 Praqma)

          Florian Reinhard created issue -
          Bue Petersen made changes -
          Summary Original: Memory map plugin fails when Linker Command FIle is not UTF-8 (Texas Instruments) New: Memory map plugin fails when Linker Command FIle is not UTF-8 (Texas Instruments) (case 12990 Praqma)
          Florian Reinhard made changes -
          Description Original: Steps to reproduce:
          - use a Linker command file that contains umlauts like öäü
          - save it as with this encoding: cp1252
          - run a build with jenkins
          - now you'll see that jenkins will fail, because it opens the command file as utf-8 and will fail to decode the umlauts

          Background:
          at least the Texas Instruments C6000 Code generation tools Version 6.1.x you can't even use utf-8 encoded, the linker will fail.

          Possible solutions:
          - add some magic to determine the command file encoding
          - let the user define the encoding
          - use the systems default encoding ( java:Charset.defaultCharset() )
          - try utf-8 and ascii (attached patch, low quality, just as a idea)
          New: Steps to reproduce:
          - use a Linker command file that contains umlauts like öäü
          - save it as with this encoding: cp1252
          - run a build with jenkins
          - now you'll see that jenkins will fail, because it opens the command file as utf-8 and will fail to decode the umlauts

          Background:
          Texas Instruments C6000 Code generation tools Version 6.1.x can't even use utf-8 encoded linker command files, the linker will fail.

          Possible solutions:
          - add some magic to determine the command file encoding
          - let the user define the encoding
          - use the systems default encoding ( java:Charset.defaultCharset() )
          - try utf-8 and ascii (attached patch, low quality, just as a idea)
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 163091 ] New: JNJira + In-Review [ 181094 ]
          Bue Petersen made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          Bue Petersen made changes -
          Resolution Original: Fixed [ 1 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          Bue Petersen made changes -
          Status Original: Reopened [ 4 ] New: Open [ 1 ]
          Bue Petersen made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            praqma Praqma Support
            freinhard Florian Reinhard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: