Actions
Bug #1159
closeddcmdump prints wrong transfer syntax for empty dataset in file
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Library and Apps
Target version:
-
Start date:
2025-05-22
Due date:
% Done:
100%
Estimated time:
Module:
dcmdata
Operating System:
Compiler:
Description
When dcmdump is run on a big-endian CPU in order to print the contents of the attached file, which contains a meta-header but no dataset, then the following output is created:
# Dicom-File-Format # Dicom-Meta-Information-Header # Used TransferSyntax: Little Endian Explicit (0002,0000) UL 202 # 4, 1 FileMetaInformationGroupLength (0002,0001) OB 00\01 # 2, 1 FileMetaInformationVersion (0002,0002) UI [1.2.276.0.7230010.3.1.0.1] # 26, 1 MediaStorageSOPClassUID (0002,0003) UI [1.2.276.0.7230010.3.1.4.1787205428.17898.1612538042.28306] # 58, 1 MediaStorageSOPInstanceUID (0002,0010) UI =LittleEndianExplicit # 20, 1 TransferSyntaxUID (0002,0012) UI [1.2.276.0.7230010.3.0.3.6.5] # 28, 1 ImplementationClassUID (0002,0013) SH [OFFIS_DCMTK_365] # 16, 1 ImplementationVersionName # Dicom-Data-Set # Used TransferSyntax: Big Endian Explicit
Note that the metaheader specifies "LittleEndianExplicit" as the transfer syntax of the main dataset, while the dataset itself reports "Big Endian Explicit".
This is a minor issue since it only affects files with empty datasets, which should never occur in practice, but is still undesirable.
Files
Updated by Marco Eichelberg 26 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Closed by commit #c514ed7ad.
Actions