I have a DICOMDIR that I'm trying to load with DcmDicomDir. I can load it properly, but there is a crash in DcmDicomDir. here is the call stack and the link to download the DICOMDIR:
http://dl.dropbox.com/u/1791478/DICOMDIR
#1 0x0000000000768877 in DcmList::deleteAllElements (this=0x1282690) at dclist.cc:290
#2 0x000000000071585e in DcmSequenceOfItems::~DcmSequenceOfItems (this=0x1282610, __in_chrg=<value optimized out>) at dcsequen.cc:95
#3 0x0000000000742af3 in DcmDirectoryRecord::~DcmDirectoryRecord (this=0x1282500, __in_chrg=<value optimized out>) at dcdirrec.cc:243
#4 0x0000000000768877 in DcmList::deleteAllElements (this=0x11bc9a0) at dclist.cc:290
#5 0x000000000071585e in DcmSequenceOfItems::~DcmSequenceOfItems (this=0x1216040, __in_chrg=<value optimized out>) at dcsequen.cc:95
#6 0x0000000000742af3 in DcmDirectoryRecord::~DcmDirectoryRecord (this=0x11b9ca0, __in_chrg=<value optimized out>) at dcdirrec.cc:243
#7 0x0000000000768877 in DcmList::deleteAllElements (this=0x1217cf0) at dclist.cc:290
#8 0x000000000071585e in DcmSequenceOfItems::~DcmSequenceOfItems (this=0x1218680, __in_chrg=<value optimized out>) at dcsequen.cc:95
#9 0x0000000000742af3 in DcmDirectoryRecord::~DcmDirectoryRecord (this=0x12260b0, __in_chrg=<value optimized out>) at dcdirrec.cc:243
#10 0x0000000000768877 in DcmList::deleteAllElements (this=0x12881f0) at dclist.cc:290
#11 0x000000000071585e in DcmSequenceOfItems::~DcmSequenceOfItems (this=0x1288170, __in_chrg=<value optimized out>) at dcsequen.cc:95
#12 0x0000000000742af3 in DcmDirectoryRecord::~DcmDirectoryRecord (this=0x121e440, __in_chrg=<value optimized out>) at dcdirrec.cc:243
#13 0x000000000074be6e in DcmDicomDir::~DcmDicomDir (this=0x121d340, __in_chrg=<value optimized out>) at dcdicdir.cc:173
DICOMDIR that caused a crash in the destructor of DcmDicomDir
Moderator: Moderator Team
-
- ICSMED DICOM Services
- Posts: 2217
- Joined: Fri, 2004-10-29, 21:38
- Location: Oldenburg, Germany
As far as I can see, the DICOMDIR is corrupt because there are offset values used for both (0004,1400) OffsetOfTheNextDirectoryRecord and (0004,1420) OffsetOfReferencedLowerLevelDirectoryEntity (e.g. 27540, 27972, 28404, 29130, 29424).
This should, of course, cause no crash in the DCMTK code, so I added this issue to our internal bug list (aka "things to do with high priority").
This should, of course, cause no crash in the DCMTK code, so I added this issue to our internal bug list (aka "things to do with high priority").
-
- DCMTK Developer
- Posts: 2505
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: DICOMDIR that caused a crash in the destructor of DcmDic
This issue has been documented as Bug #388 and fixed with commit 246cbe6 (will be visible in DCMTK's public git repository soon).
Thanks again for reporting!
Thanks again for reporting!
Who is online
Users browsing this forum: No registered users and 1 guest