Bug #374
closed
Mistake in DcmElement::changeValue() leads to Segmentation Fault
100%
Description
http://forum.dcmtk.org/viewtopic.php?t=2226
Obviously memcpy() writes to an invalid memory region (Pointer == NULL).
We need to decide what should be done with elements with invalid group lengths (i.e. if VR! = UL and/or VM != 1)
=== Update JR ===
Unfortunately the problem with 'changeValue()' cannot be reproduced any longer... even when 'putUint32Array()' is converted into a 'putUint32()'.
=== Update JR ===
See also this post on another segfault: http://forum.dcmtk.org/viewtopic.php?f=1&t=3515
Updated by Jörg Riesmeier about 13 years ago
- Category set to Library
Zum Thema "segfault" siehe auch dieses Forums-Posting: http://forum.dcmtk.org/viewtopic.php?f=1&t=3515
Updated by Andrew Chiw over 12 years ago
Mistake in DcmElement::changeValue() leads to Segmentation Fault
Description
http://forum.dcmtk.org/viewtopic.php?t=2226
Obviously memcpy() writes to an invalid memory region (Pointer == NULL).
We need to decide what should be done with elements with invalid group lengths (i.e. if VR! = UL and/or VM != 1)
=== Update JR ===
Unfortunately the problem with 'changeValue()' cannot be reproduced any longer... even when 'putUint32Array()' is converted into a 'putUint32()'.
Updated by Andrew Chiw over 12 years ago
- Subject changed from Fehler in DcmElement::changeValue() führt zu Segmentation Fault to Mistake in DcmElement::changeValue() leads to Segmentation Fault
Updated by Michael Onken over 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Fixed in commit ae4ae81.