Issues - DCMTK - OFFIS DCMTK and DICOM Projects (original) (raw)

Known issues¶

Here is a list of known issues for the various DCMTK releases1:

DCMTK 3.6.1 and newer¶

All current issues can be found in our issue tracker which can be accessed here:

http://support.dcmtk.org/redmine/projects/dcmtk

DCMTK 3.6.0¶

• 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. A first step has already been done as this commit shows.
• The OFSemaphore class (part of ''ofthread.cc'') does not work on Mac OS X since the code is not based on named semaphores as need by this OS. Therefore, the OFSemaphore code is not compiled under Mac OS X. However, thread support works in general and is enabled by the build system by default.
  • We will fix OFSemaphore for Mac OS X in one of the next snapshots.
• Due to some code changes since the last official release, the ''OFFIS_DCMTK_VERSION_NUMBER'' has become a string ("360") instead of a number (360). See forum posting for details.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• There was a wrong entry in the private tags dictionary that caused some Philips MR images to fail parsing when the dictionary is loaded. See forum posting for details.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• There was an issue with overlay planes in DICOM multi-frame images. See forum posting for details.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• There was an issue with invalid DICOM pixel data which had an odd length. Under some circumstances, e.g. transfer with storescu, DCMTK appended a padding byte twice. This caused a one-byte buffer overflow and possibly trailing garbage in the transfered image.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• Initialization of the per-module OFLogger instances is not thread-safe. Crashes can occur if multiple threads use logger objects first at the same time.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• Partial access to invalid pixel data (OW with an odd length) could fail. This manifested itself as failing network transfers.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• In the dcmsr module, content items are incorrectly added to the Structured Reporting (SR) tree when using the ''AM_beforeCurrent'' mode.
  • This will be fixed for the next release. Also see latest snapshot where this issue is already solved.
• A vulnerability has been discovered in the association negotiation code that can be abused to cause a buffer overflow. This may cause the application to crash or to possibly execute malicious code provided by the caller).
  • The issue, which is located in dcmnet/libsrc/dulparse.cc, has been fixed by commit 1b6bb76 on Dec 14, 2015. User who want to fix this vulnerability while continuing to use DCMTK 3.6.0 are advised to back-port this commit to their DCMTK 3.6.0 source tree, which is straightforward. Also see latest snapshot where this issue is already solved.

DCMTK 3.5.4¶

• 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.
• In the dcmsr module, content items are incorrectly added to the Structured Reporting (SR) tree when using the ''AM_beforeCurrent'' mode.
  • This will be fixed for the next snapshot (i.e. after ''DCMTK-3.6.1_20120515'').

1 Please note that this list does not claim to be complete and/or 100% correct. However, it might be of some help to many DCMTK users. For a detailled list of changes, we refer to the CHANGES file of the subsequent release or snapshot. Please also see our public issue tracker (created after 3.6.0) which may also list some bugs that are already applicable to 3.6.0: http://support.dcmtk.org/redmine/projects/dcmtk .