Known issues

Here is a list of known issues for the various DCMTK releases ¹⁾:

• The ––key option in findscu and movescu does not work. See FAQ #43 in order to fix this bug.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• The TIFF export in dcm2pnm and dcmj2pnm does not work on Windows systems.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• The sample worklist files are not accepted by wlmscpfs unless option ––disable-file-reject is used.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• The DICOMDIR tools dcmgpdir and dcmmkdir are not very efficient when more than a few thousand DICOM files need to be managed.
  ⇒ This will be fixed as time permits.
• The main CMakeLists.txt file does not support the latest VisualStudio compiler version (e.g. VS 2008).
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• Unlike on the command line, quotation marks are not treated as a special character inside command files (@command.txt), i.e. they cannot be used to escape space characters within a string.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• The XML tools dcm2xml and dsr2xml are not very efficient when converting data element values (e.g. TEXT content items in SR documents) which contain huge amounts of XML data.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• It is not possible to build DCMTK on some Unix-like systems if the path where DCMTK sources are located contains a space character. In that case calling “configure” stops with some errors about directories that cannot be found.
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• There is a memory leak in the extended negotiation code (only occurring if that feature is actually used).
  ⇒ This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• DCMTK seems to crash on some systems when creating new UIDs on 64 Bit Windows machines (issue not checked by OFFIS yet).
  ⇒ We will fix that for the next release or already snapshot.
• DCMTK seems to crash when compressing very large DICOM files on 64 Bit Windows machines (tested by reporting party with ~800 MB, issue not checked by OFFIS yet).
  ⇒ We will fix that for the next release or already snapshot.

• DCMTK seems to crash on some systems when creating new UIDs on 64 Bit Windows machines.
  ⇒ We will fix that for the next release or already for the next snapshot.
• DCMTK seems to crash when compressing very large DICOM files on 64 Bit Windows machines (tested by reporting party with ~800 MB, issue not checked by OFFIS yet).
  ⇒ We will fix that for the next release or already for the next snapshot.