Project

General

Profile

Actions
Copy link

Bug #745

closed

dump2dcm does not support reading private elements any more

Added by Jörg Riesmeier over 8 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
High
Assignee:
Marco Eichelberg
Category:
Application
Target version:
3.6.2
Start date:
2017-04-05
Due date:
% Done:

100%

Estimated time:
Module:
dcmdata
Operating System:
Compiler:

Description

It seems that with commit ae4ae81 dump2dcm stop from reading private elements correctly:

E: dump2dcm: test.dump: Error in creating Element: Corrupted data (line 95)

Files

ct1.dump (1.27 KB) ct1.dump Marco Eichelberg, 2017-04-17 19:42
Actions
Copy link
 #1

Updated by Michael Onken over 8 years ago

I cannot confirm this (tested with code at commit 3a7bb6b9b35a698de23d1064b36fbc31d074a1a0), do you have an example file?

Actions
Copy link
 #2

Updated by Michael Onken over 8 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #3

Updated by Marco Eichelberg over 8 years ago

The error can be reproduced using the attached dump file (on Caesar). Conversion with dump2dcm 3.6.0 works, with 3.6.1_current it fails.

Actions
Copy link
 #4

Updated by Marco Eichelberg over 8 years ago

The bug is caused by DcmItem::newDicomElement(). The version of this method previously used (which is now private) takes a DcmTag&, whereas the method used now uses a DcmTagKey& as parameter. This means that the information about the VR to be used is lost in the method call, which causes the problem.

Actions
Copy link
 #5

Updated by Marco Eichelberg over 8 years ago

  • Status changed from Feedback to Closed
  • Assignee set to Marco Eichelberg
  • % Done changed from 0 to 100

Closed by commit 73b5f8e.

Actions
Copy link

Also available in: Atom PDF