What was the exact pathname? Did it contain spaces or other special symbols?

I don't know about special characters, but it was very long ;)

Can it not be reproduced with just a long filename? It might well be that there were spaces involved..

Thomas, are you on this bug?

Difficult without windows. What about doing that Wednesday when you are also here

ok. Do you want anything special build, aside from mitkDiffusion?

problem seems to be related to the use of special symbols in the pathname

Tried importing from
Y:\Daten\diesisteinsehrsehrlangerpfadname\unddasgehtsogarnochweiter\undnochvielweitermanistderlang\vielleichtnocheineZahlenkombination0123471348975t13840756187456108276451782635918274635819072\hups

which worked, as did importing from

Y:\Daten\diesisteinsehrsehrlangerpfadname\unddasgehtsogarnochweiter\undnochvielweitermanistderlang\vielleichtnocheineZahlenkombination0123471348975t13840756187456108276451782635918274635819072\space space

for

Y:\Daten\diesisteinsehrsehrlangerpfadname\unddasgehtsogarnochweiter\undnochvielweitermanistderlang\vielleichtnocheineZahlenkombination0123471348975t13840756187456108276451782635918274635819072\_-.,;~#'+°

it did not crash, but was not able to recognize the diffusion headers

I tested on the current master.

Same behaviour for the current installer. No crash

When using special symbols nothing happens, but the system does not crash. spaces or long pathnames were no problem. On Linux it worked completely. It could also be a bug in DCMTK.

It would be helpful to know the exact pathname on which the crash occurred. The bug will remain open, but without blocking the release.

Setting target milestone to upcomming release (2013.13)

As this bug is by now a year old, could not be reproduced and no further information has been offered I am closing it. The umlaut issue could be fixed as part of T13403 .