DICOM @ OFFIS

DcmOtherByteOtherWord::createUint16Array can cause segfault if the VR of the current tag is EVR_ox. A sample code that can trigger the crash: DcmOtherByteOtherWord* pixelData = new DcmOtherByteOtherWord(DCM_PixelData); uint16_t* p; pixelData->createUint16Array(sliceSize, p); The last line should ini...

Ah, good to know! I haven't seen the dcmrecv and dcmsend commands, either. Thanks.

Sorry, I meant DcmScp, indeed. I thought, current DCMTK apps use DcmScp as base class and wanted to know if they can process simultaneous associations. Or if I implement my service based on DcmScp, whether it would be able to process simultaneous requests. But as I see, it is not actually used in cu...

Thanks, no, I haven't checked that. So, if I understand well, I can create an SCPPool that will create a new ThreadSCP for each different associations. Nice! What happens with the "regular" DcmStoreSCP? Can it handle only one association at a time and other association requests will be on ...

Hi, the documentation refers to a 'multiprocess mode' at a few places, e.g. here: https://support.dcmtk.org/docs/classDcmSCP.html#a38b0821cd090f65457a8ae6ef9e7d8c7 However, that function is not implemented (nor it's virtual, it's actually a bug), and I do not find examples in the code for handling m...

In debug mode this option has to be added to the C++ flags: /D_ITERATOR_DEBUG_LEVEL=1 The default value is 2 for debug builds, causing a crash. Unfortunately, this cannot be added to CMAKE_CXX_FLAGS_DEBUG, because it gets overwritten when building static libs, but it can be added to DCMTK_CXX11_FLAG...

I ran the tests. In release mode all the tests pass. On debug mode one test crashes because of an assertion failure inside the STL implementation of VS: This test: ofstd_OFVector Screenshot of the error: https://ibb.co/ijMWBc At this line: https://github.com/DCMTK/dcmtk/blob/DCMTK-3.6.3/ofstd/tests/...

3.6.3

It builds fine, although I did not run its tests. Compiler checks are done at configuration and build time, those do pass.

This is the first Visual Studio release that officially supports C++11 (and later standards, too), and that defines the "__cplusplus" macro accordingly. Previous versions set this macro to an archaic version number, even if they provided more or less complete C++11 support, and the /std=c+...