dcmodify crash win10

All other questions regarding DCMTK

Moderator: Moderator Team

Post Reply
Message
Author
amunaaser
Posts: 40
Joined: Thu, 2020-03-26, 10:29

dcmodify crash win10

#1 Post by amunaaser »

Hi!
dcmodify.exe sometimes crashes under Win10 Enterprise 20H2: "dcmodify.exe has stopped working. An issue caused that this program stopped working. Close the program."
Does anybody else have the same issue with this program and Win10?

Thanks in advance
Nasser Hosseini

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: dcmodify crash win10

#2 Post by Michael Onken »

Hi,

I did not see this behavior on my system so far. Do you have a call that always crashes or does even the same call only crash occasionally?

Best regards,
Michael

amunaaser
Posts: 40
Joined: Thu, 2020-03-26, 10:29

Re: dcmodify crash win10

#3 Post by amunaaser »

Hi Maichael!

This behavior I see only on some computers with Win10. It happens from the same call from within a MATLAB application. The error message comes directly from Win10 and the application stops until you click it away.

Regards
Nasser Hosseini

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: dcmodify crash win10

#4 Post by Michael Onken »

Can you provide the commandline of the call?

Update: And maybe the DICOM file you use?

amunaaser
Posts: 40
Joined: Thu, 2020-03-26, 10:29

Re: dcmodify crash win10

#5 Post by amunaaser »

Just an example:

dcmodify -ie -gin -nb -v -ea "(0008,0014)" -ea "(0008,0081)" -ea "(0008,0092)" -ea "(0008,0094)" -ea "(0008,1010)" -ea "(0008,1030)" -ea "(0008,1040)" -ea "(0008,1048)" -ea "(0008,1060)" -ea "(0008,1070)" -ea "(0008,1080)" -ea "(0008,2111)" -ea "(0010,1000)" -ea "(0010,1001)" -ea "(0010,1002)" -ea "(0010,1010)" -ea "(0010,1020)" -ea "(0010,1030)" -ea "(0010,1090)" -ea "(0010,2160)" -ea "(0010,2180)" -ea "(0010,21B0)" -ea "(0010,4000)" -ea "(0018,1030)" -ea "(0020,4000)" -ea "(0040,0275)" -ea "(0040,A730)" -ea "(0088,0140)" -ea "(0018,1000)" -ea "(0018,1030)" -ea "(3006,00C2)" -ea "(0008,0021)" -ea "(0008,0023)" -ea "(0008,002A)" -ea "(0008,0031)" -ea "(0008,0033)" -ea "(0040,0241)" -ea "(0040,0244)" -ea "(0040,0245)" -ea "(0040,0250)" -ea "(0040,0251)" -ea "(0040,0253)" -ea "(0040,0254)" -ea "(0008,0012)" -ea "(0008,0013)" -ea "(0032,1032)" -ea "(0038,0010)" -ea "(0038,0300)" -ea "(0032,1033)" -ea "(0040,0275)" -ma "(0008,0050)=" -ma "(0008,0080)=" -ma "(0008,0090)=" -ma "(0008,1050)=" -ma "(0008,1155)=" -ma "(0010,0040)=" -ma "(0020,0010)=" -ma "(0032,1030)=" -ma "(0032,4000)=" -ma "(0040,1002)=" -ma "(0040,2017)=" -ma "(0008,0018)="1.3.6.1.4.1.9590.100.1.2.70251532612204124321674292703969485714 -ma "(0020,0200)="1.3.6.1.4.1.9590.100.1.2.345800442612422251121496821011106650533 -ma "(0040,A124)="1.3.6.1.4.1.9590.100.1.2.124384711912674037836641957331875741878 -ma "(3006,0024)="1.3.6.1.4.1.9590.100.1.2.304746830112567418731207241033720758747 -ma "(3006,00C2)="1.3.6.1.4.1.9590.100.1.2.266975477112303006730293157471254551105 -ma "(0020,000D)="1.3.6.1.4.1.9590.100.1.2.258893237211083841938662027842282028967 -ma "(0020,000E)="1.3.6.1.4.1.9590.100.1.2.295332587111853751424400001280141282629 -ma "(0010,0020)="xxx -ma "(0010,0030)="19630101 -ma "(0010,0032)="12:00:00 -ma "(0010,0010)="xxx -ma "(0008,0020)="20160219 -ma "(0008,0030)="080223 -ma "(0008,103E)=" C:\DicomResult\bfr2loc_2.16.840.1.113669.632.10.99.1014.4511.23827.475085455\DICOM\DXo.2.16.840.1.113669.632.10.20160219.80223265.1521379.224.dcm

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: dcmodify crash win10

#6 Post by Michael Onken »

Hi,

your quoting looks a bit weird when you use the -ma option. The safest way is to quote the full option value, i.e. instead of

Code: Select all

-ma "(0010,0032)="12:00:00
quote it like

Code: Select all

-ma "(0010,0032)=12:00:00"
This also applies to all other option values.

Best regards,
Michael

amunaaser
Posts: 40
Joined: Thu, 2020-03-26, 10:29

Re: dcmodify crash win10

#7 Post by amunaaser »

Hi Michael!

Thank you for the reply!

The reason for quoting, as it is shown in the example, is, that "12:00:00" comes from input variable etc.
As I mentioned before, dcmodify works for me 99.99% of the cases. This crashing behaviour might be due to Win10! I really don't know. I have managed to handle it in the program, but it would be great to solve the issue correctly.

Michael Onken
DCMTK Developer
Posts: 2048
Joined: Fri, 2004-11-05, 13:47
Location: Oldenburg, Germany
Contact:

Re: dcmodify crash win10

#8 Post by Michael Onken »

Hi,

Ok, I would try to get the quoting right no matter where the input comes from. Otherwise the windows command line interpreter might fail to parse the command line correctly.

dcmodify should never crash so if you find a call that crashes repeatedly you can share it with me. Probably however, the command line is not correct then, so that dcmodify gets malformed option values to work with (and unfortunately crashes for that reason).

Otherwise I hope 99.99% is good enough for your use case :)

Best regards,
Michael

amunaaser
Posts: 40
Joined: Thu, 2020-03-26, 10:29

Re: dcmodify crash win10

#9 Post by amunaaser »

Hi Michael!

All right! That sounds logical. I will review the commands...

Wow! "...should never crash..." is a little bit strong :) In the programming world, everything is possible. :D

And 99.99% is actually OK for me!

Thanks again for your replies and have a nice day!

Mach's gut!
/Nasser

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 1 guest