On Tuesday 05 December 2006 17:21, Roland Marcus Rutschmann wrote: > On Tuesday 05 December 2006 14:33, David Baron wrote: > > On Tuesday 05 December 2006 12:24, Roland Marcus Rutschmann wrote: > > > Hi, > > > > > > just checked with all available DICOM files available to me. Could you > > > please send me an example DICOM file that provokes the segfault. Which > > > program did produce that DICOM file? > > ... > > > Here is one of them, produced by a "Diadisk" x-ray package. Note that > > another program, Kradview, flags an unknown code and then crashes itself > > by choice. Should be easy enough to simply accept and pass it. > > Hi again > > it is reproducable here now. Apparently no program I know of can handle > that file (which doesn't excuse the segfault). I'll pass it upstream.
Aeskulap works with these files just fine. This one is probably the most recently updated code. > > the header doesn't seem to be standard conform. Maybe the format uses > compressed jpeg which medcon cannot handle anyway IIRC . The other program with which I have played is a KDE Kradview. I modified it to not choke on unknown codes. Problem with unkown codes is the size number since this may be absurd. The final code before I could no longer process had a size of over 2 billion (in other words 0xFFFF). -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
