CT Object Crash

[imanabu]

EDIT: This issue is a duplicate of #48. Fixed in 1.1.0

I have a CT Object that causes a crash on fo-dicom but not on dcm4che3, dcmtk/dcmdump and dvtk editor. The crash can be demonstrated with the Dump tool, but also occurs in other DICOM store operations.

Make: Philips Brilliance 64 but has various additional private data in it potentially massaged by Primordial and also has various ELSCINT private data.

It exceptions in parsing an SQ element, but by the time this happens, the tag is all incorrect and with a huge length of 375816198.

I will be performing the initial diagnostics and if able to fix will place a pull request.

If you need to see the object, please email me directly to manabu (at) wingumd.com. Though object is sanitized, I will play it safe as it is an actual acquired object.

[anders9ustafsson]

Hello Manabu,

and many thanks for reporting. I would very much like to have a look at the object, if you could please e-mail it to "anders at cureos dot com", that would be great.

Which fo-dicom version have you tested upon? We have solved a possibly related issue in the latest pre-release, please see issue #47 . The pre-release is available on NuGet, see here.

Best regards,
Anders @ Cureos

[imanabu]

Andres, I will send you the object file in email shortly. I pulled/built the master at

862fe7d

Before I do anything else, let me pull the latest dev commit and try again.

[imanabu]

The latest development branch does fix this issue (awesome!).

[anders9ustafsson]

Great, glad to hear that, Manabu!